[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <b6530d49-074d-ee68-ed87-57c9d60d4847@infradead.org>
Date: Sat, 11 Mar 2023 08:52:53 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: Ajay Garg <ajaygargnsit@...il.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Cc: Jason Wessel <jason.wessel@...driver.com>,
Daniel Thompson <daniel.thompson@...aro.org>,
Douglas Anderson <dianders@...omium.org>,
kgdb-bugreport-request@...ts.sourceforge.net
Subject: Re: How to resolve "nptl-signals.h : no such file or directory"
+add some kernel gdb people + list
On 3/11/23 08:00, Ajay Garg wrote:
> Hi All.
>
> (Sorry had to write to this list, as the subscription to
> gdb@...rcewave.org seemingly went successful, but never got the
Is that @sourceware.org ?
> 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@...ry=6) at ../sysdeps/unix/sysv/linux/raise.c:48
> #2 0x0088cb78 in __GI_abort () at abort.c:89
> #3 <frame with modified names> 0x049b3a54 in func_1 (ffp=<optimized
> out>, base_name=<optimized out>, max_size=<optimized out>,
> file_type=<optimized out>) 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
--
~Randy
Powered by blists - more mailing lists