From: Michael Elizabeth Chastain <mec@shout.net>
To: david@streamline-computing.com, gdb-patches@sources.redhat.com
Cc: ac131313@redhat.com
Subject: Re: Patches to improve Fortran support
Date: Mon, 13 Jan 2003 17:54:00 -0000 [thread overview]
Message-ID: <200301131753.h0DHrfm17574@duracef.shout.net> (raw)
Hi David,
> This solves a pretty major problem where an array is passed as a
> parameter to a function with an underspecified dimension (ie. real
> (10:*) ) because the * is translated to '-1' which then completely
> screws up the allocation of memory.
This is great, we have a longstanding PR on this:
http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&database=gdb&pr=3
gdb segfaults associated with FORTRAN (g77) array arguments
I can review this patch later this week (Wednesday or Thursday).
Someone else might be able to get to it before then.
Do you have a copyright assignment on file with the Free Software
Foundation?
Andrew C, do you think that this patch is big enough that an
assignment is needed?
Michael C
next reply other threads:[~2003-01-13 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-13 17:54 Michael Elizabeth Chastain [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-15 21:32 David Lecomber
2003-01-13 16:58 David Lecomber
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=200301131753.h0DHrfm17574@duracef.shout.net \
--to=mec@shout.net \
--cc=ac131313@redhat.com \
--cc=david@streamline-computing.com \
--cc=gdb-patches@sources.redhat.com \
/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