Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jim Blandy <jimb@redhat.com>
To: gdb-patches@sources.redhat.com
Subject: PATCH: clean up misapplied patch to dwarf2read.c
Date: Wed, 28 Jan 2004 05:51:00 -0000	[thread overview]
Message-ID: <vt2r7xk4o4x.fsf@zenia.home> (raw)


Committed as obvious.

2004-01-27  Jim Blandy  <jimb@redhat.com>

	Clean up misapplied patch:
	* dwarf2read.c (determine_prefix): Change one of the two forward
	declarations for 'determine_prefix_aux' to a declaration for this.
	(read_func_scope): Use cu->language, not cu_language.  Pass 'cu'
	argument to 'die_specification'.

Index: gdb/dwarf2read.c
===================================================================
RCS file: /cvs/src/src/gdb/dwarf2read.c,v
retrieving revision 1.127
diff -c -r1.127 dwarf2read.c
*** gdb/dwarf2read.c	27 Jan 2004 20:47:20 -0000	1.127
--- gdb/dwarf2read.c	28 Jan 2004 04:01:22 -0000
***************
*** 765,771 ****
  
  static void read_type_die (struct die_info *, struct dwarf2_cu *);
  
! static char *determine_prefix_aux (struct die_info *die, struct dwarf2_cu *);
  
  static char *determine_prefix_aux (struct die_info *die, struct dwarf2_cu *);
  
--- 765,771 ----
  
  static void read_type_die (struct die_info *, struct dwarf2_cu *);
  
! static char *determine_prefix (struct die_info *die, struct dwarf2_cu *);
  
  static char *determine_prefix_aux (struct die_info *die, struct dwarf2_cu *);
  
***************
*** 2169,2177 ****
    if (name == NULL || !dwarf2_get_pc_bounds (die, &lowpc, &highpc, cu))
      return;
  
!   if (cu_language == language_cplus)
      {
!       struct die_info *spec_die = die_specification (die);
  
  	  /* NOTE: carlton/2004-01-23: We have to be careful in the
  	     presence of DW_AT_specification.  For example, with GCC
--- 2169,2177 ----
    if (name == NULL || !dwarf2_get_pc_bounds (die, &lowpc, &highpc, cu))
      return;
  
!   if (cu->language == language_cplus)
      {
!       struct die_info *spec_die = die_specification (die, cu);
  
  	  /* NOTE: carlton/2004-01-23: We have to be careful in the
  	     presence of DW_AT_specification.  For example, with GCC


                 reply	other threads:[~2004-01-28  5:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=vt2r7xk4o4x.fsf@zenia.home \
    --to=jimb@redhat.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