.
> It looks like a GDB bug. GDB contains code to recognize when the
> "pthreads" shared library has been loaded. When this happens, it sets
> itself up to properly handle threads (including setting up correct
> SIG32 signal handling). If you trick GDB into thinking "pthreads"
> hasn't been lo
Petr,
Thanks for testing this and finding a working counterexample! I am still
professionally interested to know if the difference is that you are
running a 2.4 kernel, or the glibc. Anyone running a 2.2 kernel with
glibc 2.2 want to drop me a line?
-Peter
(gdb) run
...
[New Thread 25452]
On Fri, 8 Dec 2000, Alan Cox wrote:
> > I have seen two failure modes: on my machine (linux 2.2.5-22, glibc
> > 2.1.1), when run under gdb 5.0, the created pthreads stick around as
> glibc 2.1.1 definitely has problems with several bits of pthreads. You
> want 2.1.3 or higher I believe.
So you'r
e the bug is? And, if the bug is in my code, I will be both relieved
and happy, and look forward to finding out what it is. If it's a kernel
bug, I submit that this makes pthreads unusable, and want to inquire if
anyone is working on fixing this?
Peter Berger, Network Dilett
4 matches
Mail list logo
