Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Pinski <pinskia@physics.uc.edu>
To: gdb-patches@sources.redhat.com, "J. Brobecker" <brobecker@gnat.com>
Cc: Andrew Pinski <pinskia@physics.uc.edu>
Subject: Re: [RFC/dwarf-2] Add support for included files
Date: Mon, 03 May 2004 22:15:00 -0000	[thread overview]
Message-ID: <6D50AA83-9D4F-11D8-9EB6-000393A6D2F2@physics.uc.edu> (raw)

I try to test building gdb with the mainline of gcc and it fails
to compile with the following error:

/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

Could you fix the problem, please?

Thanks,
Andrew Pinski


2004-04-30  J. Brobecker  <brobecker@gnat.com>

         * dwarf2read.c (line_header): Add new included_p field in
         field file_names.
         (partial_die_info): New field has_stmt_list. New field 
line_offset.
         (dwarf2_create_include_psymtab): New function.
         (dwarf2_build_include_psymtabs): New function.
         (add_file_name): Add forward declaration. Initialize new field.
         (dwarf_decode_lines): Add new parameter. Enhance this procedure
         to be able to determine the list of files included by the
         given unit, and build their associated psymtabs.
         (dwarf2_build_psymtabs_hard): Build the psymtabs for the 
included
         files as well.
         (psymtab_to_symtab_1): Build the symtabs of all dependencies as 
well.
         (read_file_scope): Update call to dwarf_decode_lines.
         (read_partial_die): Handle DW_AT_stmt_list attributes.


             reply	other threads:[~2004-05-03 22:15 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-03 22:15 Andrew Pinski [this message]
2004-05-04  0:15 ` Joel Brobecker
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=6D50AA83-9D4F-11D8-9EB6-000393A6D2F2@physics.uc.edu \
    --to=pinskia@physics.uc.edu \
    --cc=brobecker@gnat.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