Duncan Missimer <dmissimer@rhapsodynetworks.com> writes:

>  <<sigsegv.c>>  
> 
> //	
> //	When the following program is compiled on i386, all
> //	three methods of triggering a core dump produce a
> //	core file from which gdb can print a stack trace.
> //	On PPC, only the third method (assignment via a bad
> //	pointer) does so. Anybody know why?

Hm. On my laptop (apple iBook, G3/500, nathanw_sa branch), I get
backtraces for all three. I suspect you're tripping over the problem
that GDB couldn't handle tracing inside of shared libraries, which I
committed a fix for very recently.

        - Nathan