Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 05A2DC6FD1C for ; Sat, 11 Mar 2023 16:01:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230410AbjCKQBA (ORCPT ); Sat, 11 Mar 2023 11:01:00 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:58092 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230378AbjCKQA5 (ORCPT ); Sat, 11 Mar 2023 11:00:57 -0500 Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ABF8E199C1 for ; Sat, 11 Mar 2023 08:00:55 -0800 (PST) Received: by mail-ed1-x52a.google.com with SMTP id ek18so1347712edb.6 for ; Sat, 11 Mar 2023 08:00:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678550453; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=zH3H4cxNgLOQ6PFJEhsV6rqCe5ksnzMYlcew81Qs5YU=; b=PngSGwZsDShXVr2eFlFeY3I3Tx3pEZMIXHzH2KD0FPx/YRHaQFK4BHmTnrdTZUZhu9 EJsgCESZcnTR0HvbFH+XnfWR6n7Vnqo43C9o0+biTBKUI8RNSXsTyK0kWe+X3Xno8jmY tDCl4MwDroXcXFz+l6Uz++zEVfGuqjRf06N0Rq1QV+Quh8SUcDQfg19xsfkn1V0Giumd EsuZnnRxKdoKAYFjDHuc9Emk78nxs8+D0M86lo2RYxrBCmoKc14MiPtr0gugSY6onjtz QH9R9mSaCVOLd3GnF4c2/DYzkxXIPP4ZJ5zPYmjSQUjMQMz7IU3bpRtUmjv0WQdkhdud jPyA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678550453; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=zH3H4cxNgLOQ6PFJEhsV6rqCe5ksnzMYlcew81Qs5YU=; b=RxLcfdnCIZiUmuL4GtkcpUVTIddhhKY0vOJ55NXTNmg+Uc75AieR061adQjvhe05Vw 06VbGj3DA8XQAuZ08CounQmPYUjt/4sbgO0yrD93LG7RpHOHxYByvkXjgMQ5JxwtkaG7 JlNlC/Xwwkn5cGmjPNPoRV4g7dh2d6VOrKNkFPPyvH3cXJxMqEx4rdUJQBGdc6dcPLgJ SV6dCSSlQ0xXZUCsKpVArcB55NQwIJO44KuSE3QwCwkqr8g7vsAB6/Tn3AIj00OBo4NM n12vSLZupWbs1S2w7Y1B6xygEByMibe+c2N85Ve4cM2bvcijDfiadkZL1gE7ajWTrDBw /g9g== X-Gm-Message-State: AO0yUKXbJyFiK2TAmtp8X6zziIjc4G/kydkMsLgVz+fd170Z2DViMUrX MlBGzCvyew+Krd+S0cK979XBdrxFOlC7pnnFJ6pvTGYFb98= X-Google-Smtp-Source: AK7set+TKUXSTGTiK6vs4/Gq44oEikuQzFpxn3fDuxxc/wOcRb/CJkPOocwIsXWXzOAOPvdq60nsIDFnb5YmDd+1kI0= X-Received: by 2002:a50:baa6:0:b0:4ad:6052:ee90 with SMTP id x35-20020a50baa6000000b004ad6052ee90mr15939167ede.7.1678550453304; Sat, 11 Mar 2023 08:00:53 -0800 (PST) MIME-Version: 1.0 From: Ajay Garg Date: Sat, 11 Mar 2023 21:30:40 +0530 Message-ID: Subject: How to resolve "nptl-signals.h : no such file or directory" To: Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi All. (Sorry had to write to this list, as the subscription to gdb@sourcewave.org seemingly went successful, but never got the confirmation email. Even sending emails get bounced). I have been trying to analyze a core, but unable to receive the complete backtrace due to following error : ####################################### #0 0x0088ad6c in __libc_signal_restore_set (set=0xf48f2a78) at ../sysdeps/unix/sysv/linux/nptl-signals.h:79 79 ../sysdeps/unix/sysv/linux/nptl-signals.h: No such file or directory. ####################################### Following is the (incomplete) backtrace : ####################################### [Current thread is 1 (LWP 7491)] (gdb) bt #0 0x0088ad6c in __libc_signal_restore_set (set=0xf48f2a78) at ../sysdeps/unix/sysv/linux/nptl-signals.h:79 #1 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:48 #2 0x0088cb78 in __GI_abort () at abort.c:89 #3 0x049b3a54 in func_1 (ffp=, base_name=, max_size=, file_type=) at a/b/c/d/e:58 #4 0x00000270 in ?? () (gdb) ####################################### Since GDB is able to find raise.c, I did a full base-machine search for it, via : ####################################### find / -name raise.c 2> /dev/null ####################################### but could not find raise.c either on the base-machine filesystem. So, following are my queries : 1. Where are raise.c, nptl-signals.h etc. supposed to reside? 2. How can we bring back the missing nptl-signals.h file? Will be grateful for pointers. Thanks and Regards, Ajay