Path: news.net.uni-c.dk!not-for-mail From: Erik Corry Newsgroups: comp.lang.beta Subject: Re: Seg fault on x86 (maybe a newbie question) Date: Fri, 23 Nov 2001 08:07:53 +0000 (UTC) Organization: =?ISO-8859-1?Q?Mj=F8lner?= Informatics A/S Lines: 26 Sender: Erik Corry Message-ID: <9tl04o$i6c$1@news.net.uni-c.dk> References: <3BFDC150.3B9BEE82@subraumanomalie.de> NNTP-Posting-Host: amigo.cs.au.dk X-Trace: news.net.uni-c.dk 1006502873 18636 130.225.16.13 (23 Nov 2001 08:07:53 GMT) X-Complaints-To: usenet@news.net.uni-c.dk NNTP-Posting-Date: Fri, 23 Nov 2001 08:07:53 +0000 (UTC) User-Agent: tin/1.5.7-20001104 ("Paradise Regained") (UNIX) (IRIX64/6.5 (IP27)) Xref: news.net.uni-c.dk comp.lang.beta:13055 Stefan Tomlik wrote: > I continue to have the problem described above on all linux - x86 > platforms I've > ever used so far (including glibc2.1, 2.2) and different distributions, > i.e. Redhat, > Slackware, Debian and so on. We just fell over this one ourselves. :-( As far as we can see it's a problem with binutils. Existing programs work fine on new distributions, but there's a problem linking new ones which shows up when the runtime linker tries to start a program. We generate our own .o files (don't use gas) so there may have been a subtle change in their format that is biting us here. We know binutils 2.11.90.0.31-1 (shipped with Debian Woody) has the problem, and we know that binutils-2.10.91.0.2-3 (shipped in Red Hat 7.1) doesn't have the problem. We are working on finding a solution, and we aim to solve this problem before the next release. -- Erik Corry corry@mjolner.dk