This is the mail archive of the libc-hacker@cygnus.com mailing list for the glibc project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]

Re: A new pthread patch


> 
> On Sun, 7 Feb 1999 21:00:28 -0800 (PST), H.J. Lu wrote:
> >Hi,
> >
> >I don't like to call __libc_allocate_rtsig () for thread signals. It
> >is very unreliable for gdb. Here is my patch for linuxthreads. It moves
> >thread signals to glibc, which will be initialized at the link time. I
> >will send you a patch for glibc in another email.
> 
> Isn't it a bit late to be breaking the debugger interface?  I don't
> like the idea that libc 2.1 will only work with gdb .0.11 and vice
> versa, the distribution people will hate it.

It is not too late to get things right. BTW, gdb 4.17.0.11 will
work with thread in glibc 2.0. The problem is gdb 4.17.0.10 calls
__libc_allocate_rtsig () to debug thread in glibc 2.1. I want to
remove __libc_allocate_rtsig () calls in gdb 4.17.0.11 ASAP.

> 
> If you really want a more reliable debugger interface, make like the
> dynamic linker: put a stub function on the interesting path and teach
> gdb to set an internal breakpoint at it.  That's back compatible since
> gdb can fall back to the old way if the stub isn't there.
> 

It won't be easy and will be hard since gdb likes to setup signals
befor running the debugged binary.


-- 
H.J. Lu (hjl@gnu.org)


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]