public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: sjs@essex.ac.uk
To: gcc-gnats@gcc.gnu.org
Subject: ada/8924: gnatchop fails with EXCEPTION_ACCESS_VIOLATION
Date: Fri, 13 Dec 2002 05:06:00 -0000	[thread overview]
Message-ID: <20021213130506.19404.qmail@sources.redhat.com> (raw)


>Number:         8924
>Category:       ada
>Synopsis:       gnatchop fails with EXCEPTION_ACCESS_VIOLATION
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Fri Dec 13 05:06:02 PST 2002
>Closed-Date:
>Last-Modified:
>Originator:     Steve Sangwine, University of Essex, UK
>Release:        gcc 3.2
>Organization:
>Environment:
Windows 2000
MinGW 2.0.0-3
>Description:
gnatchop fails to chop the file given with this report.
>How-To-Repeat:
Run gnatchop on the attached file. When I do so, it fails to chop the file as it should and halts with an exception access violation.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-12-13 13:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-13  5:06 sjs [this message]
2003-05-12 16:56 Dara Hazeghi

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=20021213130506.19404.qmail@sources.redhat.com \
    --to=sjs@essex.ac.uk \
    --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).