Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Lucy Zhang <lucyz@uclink4.berkeley.edu>
Cc: gdb@sources.redhat.com
Subject: Re: multi-thread debugging not working
Date: Tue, 16 Jul 2002 18:41:00 -0000	[thread overview]
Message-ID: <20020717014109.GA7961@nevyn.them.org> (raw)
In-Reply-To: <002201ea89ac$0bfdbce0$9a0a0109@zhangl>

On Tue, Jul 16, 2002 at 04:55:57PM -0700, Lucy Zhang wrote:
> Hi,
> 
> 
> Yes, the newer version of GDB solved the previous problem.
> 
> Now I have a new problem with not being able to debug my multi-threaded
> program. I'm debugging using an ELF core dump that was coverted from another
> format. The program i'm debugging has about 20 threads. It may be because
> the ELF file i'm creating is missing certain information. Right now I'm at a
> loss as to what could be missing which GDB might be looking for in order to
> see the multiple threads. Does anyone have any ideas on how GDB recognize
> threads from an ELF core dump?

There should be a PT_NOTE section (or two or three of them) for every
single thread, containing its registers.  Most GNU/Linux systems at
least do not dump adequate information; you'll have to investigate your
dump format/conversion.



> 
> Below is the output from GDB:
> ----------------------------------------
> /work/lucy/gdb-5.2/gdb > ./gdb
> GNU gdb 5.2
> Copyright 2002 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i686-pc-linux-gnu".
> Setting up the environment for debugging gdb.
> .gdbinit:5: Error in sourced command file:
> No symbol table is loaded. Use the "file" command.
> (gdb) file /work/lucy/lucy1_0524/src/user/elf/vlio_test8.020715.042017
> Reading symbols from
> /work/lucy/lucy1_0524/src/user/elf/vlio_test8.020715.042017...done.
> (gdb) core-file /work/lucy/lucy1_0524/src/user/elf/elf.020715.042017
> Core was generated by `vlio_test8'.
> Program terminated with signal 4, Illegal instruction.
> Reading symbols from /lib/i686/libpthread.so.0...done.
> Loaded symbols for /lib/i686/libpthread.so.0
> Reading symbols from /lib/i686/libm.so.6...done.
> Loaded symbols for /lib/i686/libm.so.6
> Reading symbols from /usr/lib/libpopt.so.0...done.
> Loaded symbols for /usr/lib/libpopt.so.0
> Reading symbols from /lib/i686/libc.so.6...done.
> Loaded symbols for /lib/i686/libc.so.6
> Reading symbols from /lib/ld-linux.so.2...done.
> Loaded symbols for /lib/ld-linux.so.2
> #0 0x40091aa5 in sigset (sig=-1073747472, disp=0x20) at
> ../sysdeps/posix/sigset.c:69
> 69 ../sysdeps/posix/sigset.c: No such file or directory.
> in ../sysdeps/posix/sigset.c
> 
> (gdb) info threads
> * 1 process 1491 0x40091aa5 in sigset (sig=-1073747472, disp=0x20)
> at ../sysdeps/posix/sigset.c:69
> (gdb) thread 0
> Thread ID 0 not known.
> (gdb) thread 2
> Thread ID 2 not known.
> (gdb) thread 3
> Thread ID 3 not known.
> (gdb)
> 
> Thanks,
> Lucy
> 
> 
> ----- Original Message -----
> From: "Daniel Jacobowitz" <drow@mvista.com>
> To: "Lucy Zhang" <lucyz@uclink4.berkeley.edu>
> Cc: <gdb@sources.redhat.com>
> Sent: Tuesday, July 16, 2002 1:23 PM
> Subject: Re: problem loading libpthread.so
> 
> 
> > On Tue, Jul 16, 2002 at 01:17:05PM -0700, Lucy Zhang wrote:
> > > Hi,
> > >
> > > I used GDB to debug an ELF core dump which was converted from a
> different
> > > formatted dump. However when I run GDB I get the following error:
> > > This GDB was configured as "i386-redhat-linux"...
> > > Core was generated by `vlio_test8'.
> > > Program terminated with signal 4, Illegal instruction.
> > > Reading symbols from /lib/i686/libpthread.so.0...done.
> > >
> > > warning: Unable to set global thread event mask: generic error
> > > Segmentation fault (core dumped)
> >
> >
> > > Does anyone know what may have caused the seg fault. I'm not very
> familiar
> > > with GDB at all. So if anyone has any guess or intuitions about the
> cause of
> > > this problem please share.
> >
> > You need to get a newer version of GDB.  Check 5.2, from
> > http://sources.redhat.com/gdb/, and see if that works better.
> >
> > --
> > Daniel Jacobowitz                           Carnegie Mellon University
> > MontaVista Software                         Debian GNU/Linux Developer
> 
> 

-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2002-07-17  1:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-16 13:16 problem loading libpthread.so Lucy Zhang
2002-07-16 13:23 ` Daniel Jacobowitz
2002-07-16 16:54   ` multi-thread debugging not working Lucy Zhang
2002-07-16 18:41     ` Daniel Jacobowitz [this message]
2002-07-17 15:08     ` Jim Blandy
2002-07-17 16:30       ` Lucy Zhang
2002-07-18 14:55         ` Jim Blandy
2002-07-16 19:05 Lucy Zhang
2002-07-16 19:08 ` Daniel Jacobowitz
2002-07-17 12:54   ` Lucy Zhang

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20020717014109.GA7961@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=lucyz@uclink4.berkeley.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox