public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: bauhaus@futureaps.de To: gcc-gnats@gcc.gnu.org Subject: ada/10359: GNAT BUG box, 3.15p, Windows Date: Tue, 08 Apr 2003 23:46:00 -0000 [thread overview] Message-ID: <20030408234019.24022.qmail@sources.redhat.com> (raw) >Number: 10359 >Category: ada >Synopsis: GNAT BUG box, 3.15p, Windows >Confidential: no >Severity: serious >Priority: medium >Responsible: unassigned >State: open >Class: sw-bug >Submitter-Id: net >Arrival-Date: Tue Apr 08 23:46:00 UTC 2003 >Closed-Date: >Last-Modified: >Originator: bauhaus@futureapps.de >Release: gcc version 2.8.1 >Organization: >Environment: PROCESSOR_ARCHITECTURE=x86 PROCESSOR_IDENTIFIER=x86 Family 6 Model 7 Stepping 3, GenuineIntel OS=Windows_NT (5.00.2195, SP2) Reading specs from e:\GNAT\lib\gcc-lib\pentium-mingw32msv\2.8.1\specs Path=e:\GNAT\bin;... >Description: O:\temp\2>gnatmake e gcc -c e.adb +===========================GNAT BUG DETECTED==============================+ | 3.15p (20020523) (i586-pc-mingw32msv) Gigi abort, Code=104 | | Error detected at e.adb:7:20 | | Please submit bug report by email to report@gnat.com. | | Use a subject line meaningful to you and us to track the bug. | | (include your customer number #nnn in the subject line). | | 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, or FTP to your customer directory). | | See README.GNATPRO for full info on procedure for submitting bugs. | +==========================================================================+ Please include these source files with error report e.adb cmd.ads compilation abandoned gnatmake: "e.adb" compilation error >How-To-Repeat: gnatmake e >Fix: >Release-Note: >Audit-Trail: >Unformatted: ----gnatsweb-attachment---- Content-Type: text/plain; name="problem.src" Content-Disposition: inline; filename="problem.src" with cmd; procedure e is use cmd; begin execv(cmd_name, args); end e; with Interfaces.C.Strings; use Interfaces.C.Strings; package Cmd is cmd_name: constant chars_ptr; pragma Import(C, cmd_name); args: constant chars_ptr_array; pragma Import(C, args); procedure execv (filename: in chars_ptr; argv: in chars_ptr_array); pragma Import(C, execv); end Cmd; \x1a
next reply other threads:[~2003-04-08 23:46 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-04-08 23:46 bauhaus [this message] 2003-05-12 7:36 Dara Hazeghi 2003-05-12 7:36 Dara Hazeghi 2003-05-12 10:28 steven
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=20030408234019.24022.qmail@sources.redhat.com \ --to=bauhaus@futureaps.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: linkBe 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).