Dear all,

I try to use gdb to debug remotely.
I found that /init will die at sigchld_handler() function when it
catches a SIGCHLD signal and tries to write to signal_fd.
Can anyone give me some information why it has this strange situation?
Any kind of suggestion will be very appreciated.
Thanks a lot.

Regards,
Jack

On 12月8日, 下午3時23分, jack <yichang.zhu...@gmail.com> wrote:
> Hi all,
>
> I try to use strace to get more information before kernel panic.
> The following is what I got by using strace -p 1:
>
> Process 1 attached - interrupt to quit
> setup()                                 = ? ERESTART_RESTARTBLOCK (To
> be restarted)
> --- SIGCHLD (Child exited) @ 0 (0) ---
> --- SIGSEGV (Segmentation fault) @ 0 (10) ---
> Process 1 detached
>
> Do you have any idea about this and what the problem is?
> Thank in advance.
>
> Regards
> Jack
>
> On 12月4日, 下午2時41分, jack <yichang.zhu...@gmail.com> wrote:
>
>
>
> > Thanks for your help.
>
> > I have checked /proc directory but cannot find /proc/last_kmsg in
> > spite of CONFIG_ANDROID_RAM_CONSOLE=y.
>
> > In order to get more information, I call dump_stack() just before
> > calling panic("Attempted to kill init!"); in kernel/exit.c.
> > The following is the dump messages shown on the console prompt.
> > Is this information helpful for finding the problem? Thank you.
>
> > [<c0028dc4>] (dump_stack+0x0/0x14) from [<c0038f74>] (do_exit+0x26c/
> > 0x69c)
> > [<c0038d08>] (do_exit+0x0/0x69c) from [<c0039458>] (do_group_exit
> > +0xb4/0xe0)
> > [<c00393a4>] (do_group_exit+0x0/0xe0) from [<c0043830>]
> > (get_signal_to_deliver+0x394/0x3e8)
> >  r4:c7818000
> > [<c004349c>] (get_signal_to_deliver+0x0/0x3e8) from [<c002742c>]
> > (do_signal+0x58/0x4ec)
> > [<c00273d4>] (do_signal+0x0/0x4ec) from [<c00278ec>] (do_notify_resume
> > +0x2c/0x30)
> > [<c00278c0>] (do_notify_resume+0x0/0x30) from [<c0024e6c>]
> > (work_pending+0x1c/0x20)
>
> > Regards
> > Jack
>
> > On 12月4日, 上午2時38分, fadden <fad...@android.com> wrote:
>
> > > On Dec 3, 4:42 am, jack <yichang.zhu...@gmail.com> wrote:
>
> > > > Right now, it can successfully boot up and see Android main screen.
> > > > However, when I execute some applications, e.g. browser, the system
> > > > dies with kernel panic.
>
> > > Check /proc/last_kmsg after the reboot.  The details of the kernel
> > > panic should be there, assuming things haven't changed around too
> > > much.

-- 
unsubscribe: android-porting+unsubscr...@googlegroups.com
website: http://groups.google.com/group/android-porting

Reply via email to