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

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

Henry:

On Thu, Jan 27, 2011 at 12:08 PM, Henry Nestler <hen...@ar...> wrote:
>
> On 27.01.2011 05:06, Arturo R. wrote:
>>
>> #4<signal handler called>
>> #5  0xb75d5417 in ?? () from /lib/i686/cmov/libc.so.6
>> #6  0x08049f87 in print (s=0x804eb45 "\rINIT: ") at init.c:820
>> #7  0x0804a0ef in initlog (loglevel=1,
>>     s=0x804e854 "Id \"%s\" respawning too fast: disabled for %d minutes")
>>     at init.c:858
>
> You should see the text 'INIT: Id "foo" respawning too fast: disabled for 5
> minutes'.
> But the print self creates a segfault inside libc.
>
> Please locate the lines 820 to 858. Maybe the variable for the first %s has
> no value or a wrong pointer.
>
> To see the called function in libc, can you build "init" with debug and all
> libraries as static?

Attached is a backtrace with all the libraries init uses built with
debugging symbols, which gives the output I think you're looking for.

I'm stumped by another thing though. I commented out the offending
code from init.c and the system still hung, it just didn't print that
message. Does that make sense?

Thanks again for your help and patience. I'm learning a lot here that
will help me debug these kinds of things in the future.

-- 
Arturo R.