Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Ranjan Parthasarathy <Ranjan.Parthasarathy@efi.com>
To: gdb@sources.redhat.com
Subject: gdb / glibc querry
Date: Fri, 28 Sep 2001 16:17:00 -0000	[thread overview]
Message-ID: <2e613782c51fb4410d750376e9138a07@NO-ID-FOUND.mhonarc.org> (raw)

I am working on a pthreads aware gdbserver with an implementation as done in
gdb.

I have a working release however occasionally my gdbserver causes a thread to
die reporting a SIGSEGV in __DTOR_END__ . This is somewhat random and I do
not get such an error in many programs but only in certain cases but
reproducable in all such cases.

Also I found that the __DTOR_END__ is declared in some file in glibc. What is
the purpose of that and how is it used.

Any information will be really helpful

Thanks

Ranjan

------------------ Crash dump

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 14942]
0x40037342 in __DTOR_END__ () from /lib/libpthread.so.0
(gdb) info threads
  11 Thread 14951  remote_fetch: 8
0x4006597e in sigsuspend () from /lib/libc.so.6
  10 Thread 14950  remote_fetch: 8
0x080484f0 in thread6 (v=0x0) at /root/test/test-glibc.c:29
  9 Thread 14949  remote_fetch: 8
0x080485c0 in thread5 (v=0x0) at /root/test/test-glibc.c:49
  8 Thread 14948  remote_fetch: 8
0x080484d0 in thread4 (v=0x0) at /root/test/test-glibc.c:25
  7 Thread 14947  remote_fetch: 8
0x08048570 in thread9 (v=0x0) at /root/test/test-glibc.c:42
  6 Thread 14946  remote_fetch: 8
thread3 (v=0x0) at /root/test/test-glibc.c:21
  5 Thread 14944  remote_fetch: 8
0x08048654 in thread2 (v=0x0) at /root/test/test-glibc.c:62
  4 Thread 14943  remote_fetch: 8
0x080485f0 in thread1 (v=0x0) at /root/test/test-glibc.c:55
* 3 Thread 14942  remote_fetch: 8
0x40037342 in __DTOR_END__ () from /lib/libpthread.so.0
  2 Thread 14940  remote_fetch: 8
main () at /root/test/test-glibc.c:74
  1 Thread 14945  remote_fetch: 8
thread8 (v=0x0) at /root/test/test-glibc.c:38

-------------------------------------------------------


             reply	other threads:[~2001-09-28 16:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-28 16:17 Ranjan Parthasarathy [this message]
     [not found] <E15n6tZ-000761-00@crack.them.org>
2001-09-28 16:24 ` Daniel Jacobowitz
2001-09-28 16:36   ` Ranjan Parthasarathy
     [not found]   ` <200109281531.IAA21241@messenger.mvista.com>
2001-09-28 16:44     ` Daniel Jacobowitz
     [not found]   ` <200109282337.f8SNbA511877@chmls12.mediaone.net>
2001-09-28 16:53     ` Craig Rodrigues

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=2e613782c51fb4410d750376e9138a07@NO-ID-FOUND.mhonarc.org \
    --to=ranjan.parthasarathy@efi.com \
    --cc=gdb@sources.redhat.com \
    /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