Re: Problem with threaded program

[David Relson <relson@osagesoftware.com>]

At 12:28 AM 12/3/01, you wrote:
>>Daniel,
>>I don't know what the division of labor is between gdb and the kernel for 
>>situations like this, so I can't comment on that.  I can report, however, 
>>that the problem doesn't occur with gdb-4.18.  I had previously tested 
>>with an old copy of gdb-4.18.  To remove one possible difference, I have 
>>tested for the problem using copies of both gdb-4.18 and gdb-5.1 built 
>>today under the 2.4.16 kernel.  gdb-4.18 works properly and gdb-5.1 shows 
>>the problem.  If the problem is in the kernel, then 4.18 and 5.1 must be 
>>using different capabilities ...
>
>Yes, very, very different:
>
>>>The apparent 4.18 -> 5.0 ``breakage'' would have occured because GDB
>>>switched to using the thread-db/kernel interface.
>
>best way to describe this is, unfortunatly, is ``radical surgery''. While 
>the new implementation is significantly better and definitly worth the 
>effort. however, it is showing up a few teathing problems.

I believe the phrase goes "you have to break an egg to make an omelet" or 
is it that progress requires "two steps forward and one step backwards"?

>  Just make certain that your kernel/glibc are recent.

Current they are.  kernel is 2.4.16 and glibc is 2.2.4-6mdk.  I'd be 
willing to update to 2.4.17-pre2 and 2.2.4-7 if you thought it'd make a 
difference.

Is this something that ought to be brought to the attention of the kernel 
maintainers?  If so, would you notify them?  Your deeper knowledge and 
understanding of the issues involved would be helpful.

Cheers!

David