Re: gdb / thread_db / multiple ABI question

[Steve Ellcey <sellcey@cavium.com>]

On Mon, 2017-07-10 at 10:43 +0100, Pedro Alves wrote:
> > 
> > OK, setting libthread-db-search-path and debug libthread-db got me
> > a bit further.  I don't get any errors or warnings about not being
> > able to find or load libthread_db.  It's still not reading
> > everything
> > correctly though:
> > 
> > (gdb) info threads
> > Found 0 new threads in iteration 0.
> >   Id   Target Id         Frame 
> > * 3    Thread 0xf739ef70 (LWP 8660) 0x00400680 in doSomeThing ()
> >   4    Thread 0xf69bf490 (LWP 8662) warning: Couldn't find general-
> > purpose registers in core file.
> > PC register is not available
> Do you get that same warning without libthread_db?  It sounds more
> like an issue on the gdb<->bfd side than on the libthread_db side
> of things.  (Put a breakpoint on "warning".  I believe it comes from
> corelow.c:get_core_register_section.)
> 
> Thanks,
> Pedro Alves

No, without thread_db I get this:

(gdb) file m32
Reading symbols from m32...done.
(gdb) core c_32
[New LWP 79425]
[New LWP 79425]
[New LWP 79425]
warning: Unable to find libthread_db matching inferior's thread
library, thread debugging will not be available.
warning: Unable to find libthread_db matching inferior's thread
library, thread debugging will not be available.
Core was generated by `./m32'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  0x00400680 in doSomeThing ()
(gdb) info threads
  Id   Target Id         Frame 
* 3    LWP 79425         0x00400680 in doSomeThing ()



Steve Ellcey
sellcey@cavium.com