On Thu, Jul 22, 2010 at 6:21 PM, Mulyadi Santosa <mulyadi.santosa@xxxxxxxxx> wrote:
no stack trace is available. Even when I run it through the GDB. In GDB I get PC not save and that's it. I'm compiling with -O2 gcc option. When I compile with -O0 or -O1 the Problem disappears. Is it possible to be some kind of unaligned data access?
P.S.
I cannot find the "kernel:Close" in the kernel source and I don't have any clue... I've forget to mention that I am using kernel 2.6.23.17.
Best,
Zax
Hi...
Hm...no stack trace?
On Thu, Jul 22, 2010 at 23:03, Zax Zax <zaxari@xxxxxxxxx> wrote:
> Hi,
>
> I am debugging an embedded system (SH4) Application which crashes with
> "Segmentation Fault" and then the kernel message "kernel: Close" comes.
> After that the system hangs or I get the shell. I am wondering what this
> kernel: Close means. Thanks.
no stack trace is available. Even when I run it through the GDB. In GDB I get PC not save and that's it. I'm compiling with -O2 gcc option. When I compile with -O0 or -O1 the Problem disappears. Is it possible to be some kind of unaligned data access?
P.S.
I cannot find the "kernel:Close" in the kernel source and I don't have any clue... I've forget to mention that I am using kernel 2.6.23.17.
Best,
Zax
