From: Matt Zimmerman <mdz@debian.org>
To: Jeff Dike <jdike@addtoit.com>
Cc: user-mode-linux-devel@lists.sourceforge.net,
224431@bugs.debian.org, debian-gcc@lists.debian.org
Subject: Re: Resolution (Re: [uml-devel] 2.4.22-[67] problems)
Date: Wed, 7 Jan 2004 23:07:18 -0800 [thread overview]
Message-ID: <20040108070718.GI28393@alcor.net> (raw)
In-Reply-To: <200401060258.i062wWFI023087@ccure.user-mode-linux.org>
On Mon, Jan 05, 2004 at 09:58:32PM -0500, Jeff Dike wrote:
> mdz@debian.org said:
> > It turns out that this problem seems to be due to compiler
> > incompatibility. UML had been built with gcc 2.95 due to old breakage,
> > and when built with gcc 3.3 (as glibc is), everything starts working
> > again. My suspicion is that this is due to certain recent changes in
> > pthreads.
>
> Is it your opinion that there's no problem in UML itself? Having a field
> in the sigcontext getting magically munged is somewhat worrying. I'd be
> happier knowing what exactly was happening so I can be sure this wasn't
> exposing some subtle UML bug.
I was not able to come to a satisfactory conclusion as to the origin of the
problem, and once I found a solution, I stopped looking. I'm copying
debian-gcc and debian-glibc in case they're interested.
Summary for debian-{gcc,glibc}:
UML built with gcc-2.95 fails to run correctly on a current unstable system
with a 2.4 kernel. The symptoms are very strange; This started to happen recently; UML had been building
with gcc 2.95 successfully for over 9 months now with no problems.
Details are here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=224431
--
- mdz
-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
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-08 7:07 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 [this message]
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
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=20040108070718.GI28393@alcor.net \
--to=mdz@debian.org \
--cc=224431@bugs.debian.org \
--cc=debian-gcc@lists.debian.org \
--cc=jdike@addtoit.com \
--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