Re: gdb / glibc querry

Re: gdb / glibc querry

[Daniel Jacobowitz]

On Thu, Sep 27, 2001 at 05:17:58AM -0700, Ranjan Parthasarathy wrote:
> 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.

__DTOR_END__ describes the end of the static destructors section.  It's
unlikely that you're really crashing there; more likely, it's the last
symbol before the address where you are really crashing.

Are you planning on posting this code soon (I hope so!)?  Do you have a
copyright assignment in place?

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

Re: gdb / glibc querry

[Ranjan Parthasarathy]

Yes once it is working I do plan to post it and hopefully that will be soon 
enough :-).

copyright assignment ????

Thanks

Ranjan

On Friday 28 September 2001 16:25, Daniel Jacobowitz wrote:
> On Thu, Sep 27, 2001 at 05:17:58AM -0700, Ranjan Parthasarathy wrote:
> > 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.
>
> __DTOR_END__ describes the end of the static destructors section.  It's
> unlikely that you're really crashing there; more likely, it's the last
> symbol before the address where you are really crashing.
>
> Are you planning on posting this code soon (I hope so!)?  Do you have a
> copyright assignment in place?

Re: gdb / glibc querry

[Daniel Jacobowitz]

On Thu, Sep 27, 2001 at 05:36:37AM -0700, Ranjan Parthasarathy wrote:
> Yes once it is working I do plan to post it and hopefully that will be soon 
> enough :-).

Feel free to post it earlier if you want help.

> copyright assignment ????

Take a look at gdb/CONTRIBUTE for more.

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

Re: gdb / glibc querry

[Craig Rodrigues]

On Thu, Sep 27, 2001 at 05:36:37AM -0700, Ranjan Parthasarathy wrote:
> Yes once it is working I do plan to post it and hopefully that will be soon 
> enough :-).
> 
> copyright assignment ????

You need to fill out a copyright assignment form
when you contribute code to GDB.

See:
http://sources.redhat.com/gdb/contribute/
-- 
Craig Rodrigues        
http://www.gis.net/~craigr    
rodrigc@mediaone.net          

gdb / glibc querry

[Ranjan Parthasarathy]

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

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