public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: ada/7208: build of gnatlib failed with SIGILL
Date: Sun, 14 Jul 2002 03:06:00 -0000 [thread overview]
Message-ID: <20020714100603.30543.qmail@sources.redhat.com> (raw)
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.
next reply other threads:[~2002-07-14 10:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-14 3:06 Florian Weimer [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-11-19 11:58 fw
2002-07-14 3:06 Adrian Knoth
2002-07-14 1:56 Florian Weimer
2002-07-13 18:06 Adrian Knoth
2002-07-13 10:26 Florian Weimer
2002-07-04 11:46 adi
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=20020714100603.30543.qmail@sources.redhat.com \
--to=fw@deneb.enyo.de \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@gcc.gnu.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).