public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: adi@thur.de
To: gcc-gnats@gcc.gnu.org
Subject: ada/7208: build of gnatlib failed with SIGILL
Date: Thu, 04 Jul 2002 11:46:00 -0000	[thread overview]
Message-ID: <200207041842.g64IgIw12124@drcomp.erfurt.thur.de> (raw)


>Number:         7208
>Category:       ada
>Synopsis:       build of gnatlib failed with SIGILL
>Confidential:   no
>Severity:       critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jul 04 11:46:01 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     Adrian Knoth
>Release:        3.2 20020704 (experimental)
>Organization:
Thueringen Netz e.V. (www.erfurt.thur.de)
>Environment:
System: Linux drcomp 2.4.18 #13 Sun Mar 3 13:22:15 CET 2002 i586 unknown
Architecture: i586

	
host: i586-pc-linux-gnu
build: i586-pc-linux-gnu
target: i586-pc-linux-gnu
configured with: ../gcc/configure --enable-languages=c,c++,ada --enable-threads --enable-shared
>Description:
	Compiling s-auxdec.adb causes xgcc to receive SIGILL, afterwards
	leaking much memory which will end in a kill with out-of-memory
	(I've interrupted here interactively)

../../xgcc -B../../ -c -g -O2   -g -O2   -W -Wall -gnatpg -I. -I/bigspace/build/gcc/gcc/ada s-auxdec.adb
+===========================GNAT BUG DETECTED==============================+
| 3.2 20020704 (experimental) (i586-pc-linux-gnu) GCC error:               |
| internal error: Illegal instruction                                      |
| No source file position information available                            |
| Please submit bug report by email to gcc-bugs@gcc.gnu.org.               |
| Use a subject line meaningful to you and us to track the bug.            |
| Include the entire contents of this bug box in the report.               |
| Include the exact gcc or gnatmake command that you entered.              |
| Also include sources listed below in gnatchop format                     |
| (concatenated together with no headers between files).                   |
| (use plain ASCII or MIME attachment).                                    |
| See gnatinfo.txt for full info on procedure for submitting bugs.         |
+==========================================================================+

Please include these source files with error report


make[2]: *** [s-auxdec.o] Interrupt

strace -f shows:
[...]
[pid 12067] open("s-stoele.ads", O_RDONLY) = 4
[pid 12067] fstat64(4, {st_mode=S_IFREG|0644, st_size=3810, ...}) = 0
[pid 12067] read(4, "--------------------------------"..., 3810) = 3810
[pid 12067] close(4)                    = 0
[pid 12067] brk(0x8a9c000)              = 0x8a9c000
[pid 12067] --- SIGILL (Illegal instruction) ---



>How-To-Repeat:
	Do "make gnatlib" for this release
>Fix:
	No idea.
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-07-04 18:46 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-04 11:46 adi [this message]
2002-07-13 10:26 Florian Weimer
2002-07-13 18:06 Adrian Knoth
2002-07-14  1:56 Florian Weimer
2002-07-14  3:06 Adrian Knoth
2002-07-14  3:06 Florian Weimer
2002-11-19 11:58 fw

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=200207041842.g64IgIw12124@drcomp.erfurt.thur.de \
    --to=adi@thur.de \
    --cc=gcc-gnats@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).