public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "walt.brainerd at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug fortran/56581] seg fault
Date: Sun, 10 Mar 2013 16:03:00 -0000	[thread overview]
Message-ID: <bug-56581-4-wzDWPrxyMV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56581-4@http.gcc.gnu.org/bugzilla/>


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

--- Comment #2 from Walt Brainerd <walt.brainerd at gmail dot com> 2013-03-10 16:03:37 UTC ---
Sorry, I was trying lots of different experiments and apparently
removed the ! before attaching the file.

I put it back in and now cannot reproduce the error.

Ignore this for now and I will let you know if I come up with
something again that is more useful to you.

After sending the bug report, I discovered another strange thing.
The first 24? bits of the file are junk that does not show up in any
editor. "cat" shows a little open rectangle and "od" shows it.
(These files were sent to me by somebody else.)

Sorry to trouble you and thanks for the work you guys do
on gfortran.

On Sun, Mar 10, 2013 at 5:22 AM, tkoenig at gcc dot gnu.org <
gcc-bugzilla@gcc.gnu.org> wrote:

>
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56581
>
> Thomas Koenig <tkoenig at gcc dot gnu.org> changed:
>
>            What    |Removed                     |Added
>
> ----------------------------------------------------------------------------
>                  CC|                            |tkoenig at gcc dot
> gnu.org
>
> --- Comment #1 from Thomas Koenig <tkoenig at gcc dot gnu.org> 2013-03-10
> 12:22:54 UTC ---
> Unfortunately, I cannot reproduct this on Linux (also not
> with valgrind).
>
> > The code is in error as the statement function
> > is commented out, but seg error . . .
>
> > Windows 7 running under cygwin, bash.
>
> The code, as attached, has
>
> C
> MCL23200
>       AKF(A,B,E,X)=A*EXP(-B*E)*X
> MCL23210
>
> which I presume is the statement function.  It is not commented out,
> as far as I can see.
>
> Is it possible for you to run f951.exe under gdb?  This might
> give us some more information to work on.
>
> --
> Configure bugmail: http://gcc.gnu.org/bugzilla/userprefs.cgi?tab=email
> ------- You are receiving this mail because: -------
> You reported the bug.
>


  parent reply	other threads:[~2013-03-10 16:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-09 20:43 [Bug fortran/56581] New: " walt.brainerd at gmail dot com
2013-03-10 12:23 ` [Bug fortran/56581] " tkoenig at gcc dot gnu.org
2013-03-10 16:03 ` walt.brainerd at gmail dot com [this message]
2013-03-10 16:29 ` tkoenig at gcc dot gnu.org
2013-03-10 19:25 ` burnus at gcc dot gnu.org
2013-03-10 19:39 ` walt.brainerd at gmail dot com
2013-03-11 10:18 ` rguenth at gcc dot gnu.org
2013-03-11 10:51 ` [Bug fortran/56581] Segfault when reading source file which starts with a byte-order mark (-cpp works) burnus at gcc dot gnu.org
2013-03-12 22:05 ` tkoenig at gcc dot gnu.org
2013-03-13 16:13 ` walt.brainerd at gmail 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-56581-4-wzDWPrxyMV@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).