This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: ada/7208: build of gnatlib failed with SIGILL
- From: Florian Weimer <fw at deneb dot enyo dot de>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 14 Jul 2002 10:06:03 -0000
- Subject: Re: ada/7208: build of gnatlib failed with SIGILL
- Reply-to: Florian Weimer <fw at deneb dot enyo dot de>
The following reply was made to PR ada/7208; it has been noted by GNATS.
From: Florian Weimer <fw@deneb.enyo.de>
To: Adrian Knoth <adi@drcomp.erfurt.thur.de>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: ada/7208: build of gnatlib failed with SIGILL
Date: Sun, 14 Jul 2002 12:00:05 +0200
Adrian Knoth <adi@drcomp.erfurt.thur.de> writes:
>> > Yes. I've tried it with the actual cvs co, here is the result, though
>> > SIGILL changed to segfault:
>> We need a GDB backtrace of the gnat1 process when it receives SIGILL,
>> and a disassembly of the function corresponding to the topmost frame.
>
> Is it ok for you if I'll send you a statically linked version of my xgcc
> and the corefile?
The core file does not help much, unless it has been generated by
SIGILL.
> (to your personal address? I guess the gcc-list doesn't want it)
I can try it on my i586-pc-linux-gnu machine (maybe GCC really
generates an instruction invalid on i586), but I'd rather like to see
the backtrace on your machine.
> I've now deleted everything, cvs co will follow and the static
> built, too. I guess building without threads is easier for you to
> debug, isn't it?
It shouldn't matter; the compiler itself does not use the
multi-tasking run-time library.