public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ExtraLeveLInSoftware at ntlworld dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/58128] Problem using NAME (STANDARD_INPUT) in gcc-4.7.2
Date: Wed, 14 Aug 2013 12:00:00 -0000	[thread overview]
Message-ID: <bug-58128-4-dJQYmt4GoS@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-58128-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58128

--- Comment #2 from Ellis N. Thomas <ExtraLeveLInSoftware at ntlworld dot com> ---
    Further Information about the Exception

    Added extra "others" handler for Unexpected exceptions to TryStdIP3.
Compiled:
bash> gnatmake TryStdIP3.ada 
gcc -c -x ada trystdip3.ada
gnatbind -x trystdip3.ali
gnatlink trystdip3.ali

    Ran:
bash> trystdip3
TryStdIP3 from SiRiL Issue 0.22 21-Apr-1989 
Copyright (c) 2013 E.N. Thomas
Started at : 12:45:57  14/ 8/13
Try to get NAME (STANDARD_INPUT)
Try to open CommandFile using: <*stdin>

raised PROGRAM_ERROR : unhandled signal

    So the "others" handler has failed to handle this PROGRAM_ERROR!
Although it is reported as an exception, it is not able to be handled in the
normal Ada way, so this seriously compromises the ability to work around this
error.

    Consequently, a work-round such as a new version of s-fileio.adb
(system__file_io__open) and/or a-textio.adb (ada__text_io__open) would be
appreciated.

E.N. Thomas/14-Aug-2013


  parent reply	other threads:[~2013-08-14 12:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-11 19:33 [Bug ada/58128] New: " ExtraLeveLInSoftware at ntlworld dot com
2013-08-14 11:59 ` [Bug ada/58128] " ExtraLeveLInSoftware at ntlworld dot com
2013-08-14 12:00 ` ExtraLeveLInSoftware at ntlworld dot com [this message]
2013-08-14 13:02 ` ebotcazou at gcc dot gnu.org
2013-08-15 19:13 ` ExtraLeveLInSoftware at ntlworld dot com

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=bug-58128-4-dJQYmt4GoS@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@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).