[uClibc]Gdb with uClibc

[Phil Wilshire]

HI All,

On the arm platform this  can be caused by the 
save / restore of the floating point register in setjmp / longjmp.

This is drastically fixed by removing the floating point support from  uClibC configuration

A better solution would be to specify that the CPU has no fp regs...
If you agree with the analysis is there any chance for something like this to get introduced.
It would make my life a LOT easier.

best regards
  Phil Wilshire




Erik Andersen wrote:
> 
> On Wed Feb 05, 2003 at 11:21:57AM -0800, David Meggy wrote:
> > (gdb) b main
> > Breakpoint 1 at 0x819c: file HelloWorld.c, line 4.
> > (gdb) cont
> > Continuing.
> >
> > Program received signal SIGILL, Illegal instruction.
> > 0x00008088 in _start ()
> > (gdb) quit
> > The program is running.  Exit anyway? (y or n) y
> 
> I saw a similar thing last night when trying to debug a uClibc
> app on my netwinder using native gdb, so I don't think this is a
> gdbserver problem, and may in fact be a current problem with the
> uClibc ARM port.  I'm busy working at finding what the deal is,
> 
>  -Erik
> 
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--
> _______________________________________________
> uClibc mailing list
> uClibc at uclibc.org
> http://uclibc.org/mailman/listinfo/uclibc

-- 
SDCS -- System Design & Consulting Services LLC, http://www.sysdcs.com
** Embedded Linux Training **  email me for details  
630 Springhouse Sq., Leesburg VA 20175 t: 703 669 9766 f: 703 669 9768