Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: David Lecomber <david@streamline-computing.com>
To: patches <gdb-patches@sources.redhat.com>
Subject: Dwarf2 Producer info
Date: Tue, 20 Jul 2004 22:14:00 -0000	[thread overview]
Message-ID: <1090362598.21483.108.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com> (raw)

Hi

This is an obvious extension to plug a gap. 

I've some more changes to come that make use of this (specifically to
take account of broken g77) and also fix some longstanding array issues,
but I'm getting this easy one in the source before inflicting the
complex one on the world..  if anyone has a sharper eye than me for the
code formatting rules, please feel free to shout out!

Cheers 
David

2004-07-20  David Lecomber  <dsl@sources.redhat.com>

	* dwarf2read.c (set_cu_producer): New.


Index: dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.156
diff -p -r1.156 dwarf2read.c
*** dwarf2read.c	6 Jul 2004 19:29:30 -0000	1.156
--- dwarf2read.c	20 Jul 2004 22:12:07 -0000
*************** struct dwarf2_cu
*** 262,267 ****
--- 262,269 ----
    enum language language;
    const struct language_defn *language_defn;
  
+   const char* producer;
+ 
    /* The generic symbol table building routines have separate lists
for
       file scope symbols and all all other scopes (local scopes).  So
       we need to select the right one to pass to add_symbol_to_list().
*************** static char *skip_leb128 (bfd *, char *)
*** 739,744 ****
--- 741,748 ----
  
  static void set_cu_language (unsigned int, struct dwarf2_cu *);
  
+ static void set_cu_producer (const char*, struct dwarf2_cu *);
+ 
  static struct attribute *dwarf2_attr (struct die_info *, unsigned int,
  				      struct dwarf2_cu *);
  
*************** read_file_scope (struct die_info *die, s
*** 2362,2367 ****
--- 2366,2378 ----
        set_cu_language (DW_UNSND (attr), cu);
      }
  
+   attr = dwarf2_attr (die, DW_AT_producer, cu);
+   if (attr)
+     set_cu_producer (DW_STRING (attr), cu);
+   else 
+     set_cu_producer(NULL, cu);
+       
+   
    /* We assume that we're processing GCC output. */
    processing_gcc_compilation = 2;
  #if 0
*************** skip_leb128 (bfd *abfd, char *buf)
*** 5560,5565 ****
--- 5571,5582 ----
  }
  
  static void
+ set_cu_producer (const char* producer, struct dwarf2_cu *cu)
+ {
+   cu->producer = producer;
+ }
+ 
+ static void
  set_cu_language (unsigned int lang, struct dwarf2_cu *cu)
  {
    switch (lang)



             reply	other threads:[~2004-07-20 22:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-20 22:14 David Lecomber [this message]
2004-07-20 23:18 ` Daniel Jacobowitz
2004-07-20 23:40   ` David Lecomber
2004-07-21  0:09     ` Daniel Jacobowitz
2004-07-21  7:12       ` David Lecomber
2004-07-21 13:25         ` Daniel Jacobowitz
2004-07-28 19:05         ` Jim Blandy
2004-07-26 20:55 ` [RFA] Dwarf2 Producer info (dwarf2read.c) David Lecomber
2004-07-29 10:28   ` David Lecomber
2004-07-29 19:25     ` Jim Blandy

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=1090362598.21483.108.camel@cpc4-oxfd5-5-0-cust12.oxfd.cable.ntl.com \
    --to=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