From: Chris January <chris.january@allinea.com>
To: gdb-patches@sourceware.org
Subject: [PATCH] Support Fortran common blocks with addresses >INT_MAX.
Date: Thu, 08 Mar 2012 14:31:00 -0000 [thread overview]
Message-ID: <1331217037.2742.10.camel@gumtree> (raw)
The address of a Fortran common block may be >INT_MAX. fix_common_block
should be using CORE_ADDR, not int.
2012-03-08 Chris January <chris.january@allinea.com>
* stabsread.c (fix_common_block): Change type of valu argument
to CORE_ADDR.
---
Index: gdb/stabsread.c
===================================================================
--- gdb/stabsread.c.orig 2011-02-17 11:14:42.713081030 +0000
+++ gdb/stabsread.c 2011-02-17 11:15:14.414327296 +0000
@@ -104,7 +104,7 @@ static void
patch_block_stabs (struct pending *, struct pending_stabs *,
struct objfile *);
-static void fix_common_block (struct symbol *, int);
+static void fix_common_block (struct symbol *, CORE_ADDR);
static int read_type_number (char **, int *);
@@ -4805,7 +4805,7 @@ common_block_end (struct objfile *objfil
the common block name). */
static void
-fix_common_block (struct symbol *sym, int valu)
+fix_common_block (struct symbol *sym, CORE_ADDR valu)
{
struct pending *next = (struct pending *) SYMBOL_TYPE (sym);
next reply other threads:[~2012-03-08 14:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-08 14:31 Chris January [this message]
2012-03-09 19:39 ` Joel Brobecker
2012-03-12 8:45 ` Chris January
2012-03-12 15:30 ` Joel Brobecker
2012-03-12 19:30 ` Tom Tromey
2012-03-13 15:17 ` Chris January
2012-03-13 16:50 ` Joel Brobecker
2012-03-12 19:28 ` Tom Tromey
-- strict thread matches above, loose matches on Subject: below --
2012-03-08 14:31 Chris January
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=1331217037.2742.10.camel@gumtree \
--to=chris.january@allinea.com \
--cc=gdb-patches@sourceware.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