.
> 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
Peter Berger <[EMAIL PROTECTED]> writes:
>
> Hi. I have the following tiny test program which fails dramatically,
> using pthreads, in a number of fascinating ways on various version of
> linux, using various versions of glibc, under various (current) versions
> of GDB.
It looks like a GDB bug.
> So you're saying that you got this to work? Because I certainly couldn't
> get it working with a higher version either. I would really love a
I read straight down it anf realised you referenced obsolete versions of
tg->created and thus broadcast incorrectly
> I apologize for my ignorance --
Petr,
It ran fine on my stock Mandrake 7.2 system - linux-2.2.17-21mdk and
glibc-2.2-5mdk. The program ran fine in both environments - command line
and gdb-5.0. Loadavg creeps up slowly as the program continues to run. At
thread #37000, loadavb is 3.65. The ps command indicates 4 threads f
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 8 Dec 00 at 14:43, Peter Berger wrote:
> > tg->created may be out of date
> ...
> > You can create it, count it, then up tg->created out of order
>
> Well, you're right, but this is picking lint. Making this change (see
> http://peterb.telerama.com/thread-test.c for the corrected version)
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
> 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.
> zombies until the machine runs out of resources.
Hi. I have the following tiny test program which fails dramatically,
using pthreads, in a number of fascinating ways on various version of
linux, using various versions of glibc, under various (current) versions
of GDB. I am honestly not sure if this is a linux bug, a glibc bug, or a
gdb bug,
9 matches
Mail list logo
