[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: AW: AW: problem with gdb-cris

Schachner Thomas wrote:
> cris-fpless-backtrace :
> #0 0x65636376 in (null)
> Cannot access memory at ddress 0x0
> info registers :
> No selected frame.

This doesn't look good.  The core dump must be corrupt or something.  If 
I do something silly like:

int main()
    int i;

    i = *0x0;

    return 0;

backtrace and cris-fpless-backtrace shows me

(gdb) backtrace
#0  0x00080348 in main ()
(gdb) cris-fpless-backtrace
#0  0x00080348 in main
#1  0x35584a26 in __libc_start_main at ../sysdeps/generic/libc-start.c:129
#2  0x00080244 in _start

Even if your program crashed inside a library function, you should at 
least be able to see that the innermost stack frame.  I tried this with 
gdb-cris 5.3, but I'm going to try it with 5.2.1 also.

Orjan Friberg
Axis Communications