Re: [User-mode-linux-devel] segfault around execve() and others when attaching gdb

[Yann D. <yd...@al...>]

On Mon, Oct 16, 2000 at 07:11:59PM -0500, Jeff Dike wrote:
> yd...@al... said:
> > Program received signal SIGSEGV, Segmentation fault. 
> > 0x10034a70 in ?? () 
> > (gdb) symbol-file kernel-source-2.4.0-test9-um/linux 
> > Reading symbols from kernel-source-2.4.0-test9-um/linux...done. 
> > (gdb) bt #0
> > 0x10034a70 in padzero (elf_bss=1073818712)
> >     at 
> >/home/dwitch/usr/src/umlinux/kernel-source-2.4.0-test9-um/include/asm/arch/str
> ing.h:418
> > #1  0x10035349 in load_elf_interp(interp_elf_ex=0x50053d48,  
> 
> This and the others are correct.  The process is segfaulting so as to 
> demand-load itself.  To avoid seeing them, do this:
> 	handle SIGSEGV pass nostop noprint

Oops :}  Nearly forgot it was as OS running inside :)

-- 
Yann Dirson    <yd...@al...> |    Why make M$-Bill richer & richer ?
debian-email:   <di...@de...> |   Support Debian GNU/Linux:
                                    | Cheaper, more Powerful, more Stable !
http://ydirson.free.fr/             | Check <http://www.debian.org/>