On Mon, 16 Jul 2012, Donovan Watteau wrote:
> >Description:
> All threaded programs end up segfaulting on my B&W G3 (Rev 1).
> This makes most ports unusable, since a lot of ports use threads
> (or a library that links to them), i.e: they almost always crash
> at start-up.
>
> This looks specific to the G3 processor, as I'm surprised it
> hasn't been reported yet.
>
> Please see the output of base gdb [1] and gdb-7.4.1 from
> ports [2]. They come from the core-dump of the following
> "thread_eight" program.
> >How-To-Repeat:
> Here's how I tried to get some information from gdb:
> * Compile a threaded program (here, thread_eight.c [3])
> * Start compiling a port. If the machine is completely idle, the
> segfault is much harder to catch.
> * Repeatedly launch the binary. It should eventually crash and
> produce a core-dump.
> * Then, launch gdb (or egdb) on it to get some information.
...
> #0 0x9129ef30 in pthread_self () at tcb.h:60
> 60 __asm__ ("lwzx %0, %%r2, %1" : "=r" (val) : "r" (offset));
Can you show the output of "info regs" for that thread?
Philip
