I had recompiled the nand flash driver with -O0 to be able better debug with
GDB. Now I guess I have found one problem.
In lpc3180c line 519 allocates memory:
oob_buffer = malloc(6);
But later set more then allocated at line 562:
memset(oob_buffer, 0xff, (nand->page_size == 512) ? 6 : 24);
and crashes when free it at line 602:
free(oob_buffer);
So I corrected it and no crash anymore! Although not all the data written to
flash so I have to investigate it more.
Anyway it strange why gdb does not list the whole call stack after crash.
Only lists glibc's backtraces...
Richard
On Wed, Jan 6, 2010 at 1:30 PM, Øyvind Harboe <oyvind.har...@zylin.com>wrote:
> On Wed, Jan 6, 2010 at 11:43 AM, richard vegh <vegh.ri...@gmail.com>
> wrote:
> >>I think you should focus on getting the gdb symbols for the bt ...
> >
> > I would happy if I can use symbols with my own built one. Do you have any
> > hints why gdb can not use the already available symbols in the
> executable?
>
> I don't know... it should "just work"... what is the precise procedure
> you use to
> build OpenOCD?
>
>
> --
> Øyvind Harboe
> US toll free 1-866-980-3434 / International +47 51 63 25 00
> http://www.zylin.com/zy1000.html
> ARM7 ARM9 ARM11 XScale Cortex
> JTAG debugger and flash programmer
>
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
