From: Jeff Dike <jdike@addtoit.com>
To: Matt Zimmerman <mdz@debian.org>
Cc: Bill Allombert <allomber@math.u-bordeaux.fr>,
user-mode-linux-devel@lists.sourceforge.net,
176485@bugs.debian.org
Subject: Re: [uml-devel] Re: Panic with slirp transport and gcc 3.3
Date: Thu, 15 Jan 2004 21:38:34 -0500 [thread overview]
Message-ID: <200401160238.i0G2cYrf004298@ccure.user-mode-linux.org> (raw)
In-Reply-To: Your message of "Tue, 13 Jan 2004 10:51:57 PST." <20040113185156.GW1514@alcor.net>
mdz@debian.org said:
> Certainly (this is from 2.4.23-1um). Seems like something goes weird
> with procfs, but I've no idea why this only happens with slirp (and
> newer gcc for that matter).
Just tried it, boots fine here, but then I'm not playing with new gccs.
Can you send me the binary that crashes? I assume it's statically linked...
I'm thinking that something funky is happening in the initcalls, and the slirp
initcall happens to push the funkiness over the edge.
Jeff
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-01-16 2:17 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-20 1:13 [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 17:14 ` Jeff Dike
2003-12-21 0:47 ` Matt Zimmerman
2003-12-21 15:58 ` BlaisorBlade
2003-12-21 22:40 ` Matt Zimmerman
2003-12-21 23:16 ` Matt Zimmerman
2003-12-22 0:25 ` Jeff Dike
2003-12-22 4:08 ` Matt Zimmerman
2003-12-22 5:49 ` Daniel Jacobowitz
2003-12-22 9:08 ` Matt Zimmerman
2004-01-05 17:51 ` Adam Heath
2004-01-05 18:10 ` Matt Zimmerman
2003-12-24 12:48 ` BlaisorBlade
2003-12-21 0:52 ` Matt Zimmerman
2003-12-21 1:06 ` Matt Zimmerman
2003-12-28 9:33 ` Matt Zimmerman
2003-12-28 9:51 ` Matt Zimmerman
2003-12-28 9:52 ` Matt Zimmerman
2004-01-06 2:59 ` Jeff Dike
2003-12-28 10:12 ` Matt Zimmerman
2003-12-28 11:30 ` Matt Zimmerman
2003-12-30 18:43 ` Resolution (Re: [uml-devel] 2.4.22-[67] problems) Matt Zimmerman
2004-01-06 2:58 ` Jeff Dike
2004-01-06 7:41 ` Nuno Silva
2004-01-06 8:02 ` Matt Zimmerman
2004-01-06 8:20 ` Nuno Silva
2004-01-06 8:47 ` Nuno Silva
2004-01-06 9:20 ` Nuno Silva
2004-01-06 17:13 ` Matt Zimmerman
2004-01-09 7:22 ` Nuno Silva
2004-01-08 7:07 ` Matt Zimmerman
2004-01-12 18:36 ` [uml-devel] Panic with slirp transport and gcc 3.3 Matt Zimmerman
2004-01-13 15:25 ` [uml-devel] " Bill Allombert
2004-01-13 17:30 ` Jeff Dike
2004-01-13 17:44 ` Bill Allombert
2004-01-13 18:51 ` Matt Zimmerman
2004-01-16 2:38 ` Jeff Dike [this message]
2004-01-16 2:38 ` Matt Zimmerman
2004-01-16 20:04 ` Jeff Dike
2004-01-16 19:49 ` Matt Zimmerman
2004-01-17 0:42 ` Matt Zimmerman
2003-12-21 1:29 ` [uml-devel] 2.4.22-[67] problems Matt Zimmerman
2003-12-20 19:05 ` Nick Craig-Wood
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200401160238.i0G2cYrf004298@ccure.user-mode-linux.org \
--to=jdike@addtoit.com \
--cc=176485@bugs.debian.org \
--cc=allomber@math.u-bordeaux.fr \
--cc=mdz@debian.org \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).