From: Joel Brobecker <brobecker@gnat.com>
To: Andrew Pinski <pinskia@physics.uc.edu>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFC/dwarf-2] Add support for included files
Date: Tue, 04 May 2004 00:15:00 -0000 [thread overview]
Message-ID: <20040504001507.GW16083@gnat.com> (raw)
In-Reply-To: <6D50AA83-9D4F-11D8-9EB6-000393A6D2F2@physics.uc.edu>
[-- Attachment #1: Type: text/plain, Size: 957 bytes --]
> /home/gates/pinskia/src/gnu/combinesources/src/gdb/dwarf2read.c: In
> function `dwarf2_create_include_psymtab':
> /home/gates/pinskia/src/gnu/combinesources/src/gdb/dwarf2read.c:1244:
> error: invalid lvalue in assignment
Sorry about that, this error didn't show up with the compiler I used.
I just built one straight from mainline and could reproduce the error.
Apparently, expressions like this are not legal?
(char *) something = NULL;
Anyway, I fixed the immediate problem by expanding the PST_PRIVATE
macro into its actual definition, but without the cast. That should
allow you to build again.
2004-05-03 Joel Brobecker <brobecker@gnat.com>
* dwarf2read.c (dwarf2_create_include_psymtab): Fix build
failure detected by recent versions of GCC.
(psymtab_to_symtab_1): No longer use the PST_PRIVATE macro
to be consistent with the usage in dwarf2_create_include_psymtab.
Checked in mainline.
--
Joel
[-- Attachment #2: dwarf2read.c.diff --]
[-- Type: text/plain, Size: 1225 bytes --]
Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.149
diff -u -p -r1.149 dwarf2read.c
--- dwarf2read.c 3 May 2004 16:21:50 -0000 1.149
+++ dwarf2read.c 4 May 2004 00:08:10 -0000
@@ -1239,9 +1239,9 @@ dwarf2_create_include_psymtab (char *nam
/* No private part is necessary for include psymtabs. This property
can be used to differentiate between such include psymtabs and
the regular ones. If it ever happens that a regular psymtab can
- legitimally have a NULL PST_PRIVATE part, then we'll have to add a
+ legitimally have a NULL private part, then we'll have to add a
dedicated field for that in the dwarf2_pinfo structure. */
- PST_PRIVATE (subpst) = NULL;
+ subpst->read_symtab_private = NULL;
}
/* Read the Line Number Program data and extract the list of files
@@ -2109,7 +2109,7 @@ psymtab_to_symtab_1 (struct partial_symt
psymtab_to_symtab_1 (pst->dependencies[i]);
}
- if (PST_PRIVATE (pst) == NULL)
+ if (pst->read_symtab_private == NULL)
{
/* It's an include file, no symbols to read for it.
Everything is in the parent symtab. */
next prev parent reply other threads:[~2004-05-04 0:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-03 22:15 Andrew Pinski
2004-05-04 0:15 ` Joel Brobecker [this message]
2004-05-04 0:18 ` Andrew Pinski
-- strict thread matches above, loose matches on Subject: below --
2004-04-07 16:05 Jim Blandy
2004-04-13 5:20 ` Joel Brobecker
2004-04-14 19:10 ` Jim Blandy
2004-04-15 22:13 ` Joel Brobecker
2004-04-16 4:24 ` Jim Blandy
2004-04-16 4:28 ` Joel Brobecker
2004-04-16 23:08 ` Joel Brobecker
2004-04-29 23:32 ` Jim Blandy
2004-05-01 1:14 ` Joel Brobecker
2004-05-01 4:57 ` Jim Blandy
2004-05-03 16:25 ` Joel Brobecker
2004-01-02 7:25 Joel Brobecker
2004-01-02 14:18 ` Daniel Jacobowitz
2004-01-03 14:42 ` Joel Brobecker
2004-01-03 16:34 ` Eli Zaretskii
2004-01-03 17:47 ` Joel Brobecker
2004-01-02 14:45 ` Eli Zaretskii
2004-01-05 16:18 ` Andrew Cagney
2004-01-05 19:17 ` Joel Brobecker
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=20040504001507.GW16083@gnat.com \
--to=brobecker@gnat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=pinskia@physics.uc.edu \
/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