I did a GDB trace. The line was in the main kernel.
(gdb) run
(some messages)
Program received SIGSEGV, Segmentation Fault.
0x0828d047 in zlib_inflateInit2 (strm=0x84dbfe0, windowBits=15)
at lib/zlib_inflate/inflate.c:78
78 state->wrap = (windowBits >> 4) + 1;
(gdb) continue
(continues with no ethernet)
Tony
On Mon, Mar 12, 2007 at 07:09:45PM -0700, Tony wrote:
> ZLIB Compression causes a segv which is only appearent when being
> debugged. It happens arount lib/zlib_inflate/inflate.c:78 in
> zlib_inflate. Sounds like a uml kernel-code handler error. You may
> want to implement your own zlib code, or link with libz. I cannot run
> UML without ethernet.
>
> PS: For some odd reason (maybe /proc/mm?) the SEGV wasn't fatal for
> the whole kernel. Can you picture a non-fatal segv? I think it MAYBE
> is a host bug/skas bug/gcc bug.
More details on all of this? Like the information you used to figure
this out?
Jeff
--
Work email - jdike at linux dot intel dot com
____________________________________________________________________________________
Food fight? Enjoy some healthy debate
in the Yahoo! Answers Food & Drink Q&A.
http://answers.yahoo.com/dir/?link=list&sid=396545367
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
User-mode-linux-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-user
