Re: [coLinux-users] How to debug: "INIT: PANIC: segmentation violation at 0xb776c417! sleeping for 30 seconds."

[Arturo R. <ja...@gm...>]

Hi Henry.

On Wed, Jan 26, 2011 at 4:14 PM, Henry Nestler <hen...@ar...> wrote:
>
> You should have debug symbols for init, or an init with debug symbols. Than
> you can load init into gdb and locate the code snip for address 0xb766d417,
> or you can run "objdump -Dr /sbin/init >dump.txt" and find out the address
> manually. The addr2line should also work for this.
>

Thank you very much for the reply. I guess I misspoke. When I said
that the crash is reproducible all the time, I mean that putting the
laptop to standby always causes init to crash, but the address given
in the error message changes.

I've rebuilt an sysvinit package with debug symbols and I can attach
to it with gdb, but when the process crashes gdb becomes unresponsive
too.

I was able to get a coredump and I think I have a little more
information about the crash this time, but I'm not sure how to
interpret it. I've attached the output of gdb in case it's helpful to
you or anybody else.

Thanks again.

-- 
Arturo R.