Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Elena Zannoni <ezannoni@redhat.com>
To: David Carlton <carlton@math.stanford.edu>
Cc: Elena Zannoni <ezannoni@redhat.com>,
	Daniel Jacobowitz <drow@mvista.com>,
	gdb-patches@sources.redhat.com
Subject: Re: [RFA] Relocate debug information in object files (e.g. add-symbol-file) [take 2]
Date: Sat, 01 Feb 2003 01:08:00 -0000	[thread overview]
Message-ID: <15931.7952.213719.470837@localhost.redhat.com> (raw)
In-Reply-To: <ro17kckdddv.fsf@jackfruit.Stanford.EDU>

David Carlton writes:
 > On Fri, 31 Jan 2003 19:47:57 -0500, Elena Zannoni <ezannoni@redhat.com> said:
 > 
 > >> I haven't looked at it at all closely; but dwarf2_read_section (and
 > >> hence symfile_relocate_debug_section) is getting passed a NULL
 > >> section from this part of dwarf2_build_psymtabs:
 > >> 
 > >> if (dwarf_ranges_offset)
 > >> dwarf_ranges_buffer = dwarf2_read_section (objfile,
 > >> dwarf_ranges_offset,
 > >> dwarf_ranges_size,
 > >> dwarf_ranges_section);
 > >> else
 > >> dwarf_ranges_buffer = NULL;
 > >> 
 > 
 > > It's odd, if the dwarf_ranges_offset is zero, the call shouldn't be made.
 > > Maybe something is trashing the stack?
 > 
 > > What gcc did you use? I tried with 2.96 (from RHL 7.2) and didn't see
 > > the error.
 > 
 > Did you specify DWARF 2?  I saw this on 3.1.
 > 

Doh. right, I keep forgetting I am still using stabs. I definitely
need to upgrade my machine.

 > I've found the problem, though: nobody seems to be setting
 > dwarf_ranges_section!  Patch enclosed below; I'm running it through
 > the testsuite, and I'll commit it as obvious if it cures the problem.
 > 

Thanks, if it works, go ahead.

elena


 > David Carlton
 > carlton@math.stanford.edu
 > 
 > 2003-01-31  David Carlton  <carlton@math.stanford.edu>
 > 
 > 	* dwarf2read.c (dwarf2_locate_sections): Set
 > 	dwarf_ranges_section.
 > 
 > Index: dwarf2read.c
 > ===================================================================
 > RCS file: /cvs/src/src/gdb/dwarf2read.c,v
 > retrieving revision 1.81
 > diff -u -p -r1.81 dwarf2read.c
 > --- dwarf2read.c	31 Jan 2003 19:22:18 -0000	1.81
 > +++ dwarf2read.c	1 Feb 2003 00:57:49 -0000
 > @@ -1002,6 +1002,7 @@ dwarf2_locate_sections (bfd *ignore_abfd
 >      {
 >        dwarf_ranges_offset = sectp->filepos;
 >        dwarf_ranges_size = bfd_get_section_size_before_reloc (sectp);
 > +      dwarf_ranges_section = sectp;
 >      }
 >  }
 >  


  reply	other threads:[~2003-02-01  1:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-04 14:06 [RFA] Relocate debug information in object files (e.g. add-symbol-file) Daniel Jacobowitz
2002-04-15 14:11 ` Elena Zannoni
2002-04-15 14:26   ` Daniel Jacobowitz
2002-10-11  7:44 ` [RFA] Relocate debug information in object files (e.g. add-symbol-file) [take 2] Daniel Jacobowitz
2003-01-30 23:35   ` Elena Zannoni
2003-01-31 19:26     ` Daniel Jacobowitz
2003-02-01  0:09       ` David Carlton
2003-02-01  0:43         ` Elena Zannoni
2003-02-01  0:59           ` David Carlton
2003-02-01  1:08             ` Elena Zannoni [this message]
2003-02-01  1:13               ` David Carlton
2003-02-01  2:41                 ` Daniel Jacobowitz

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=15931.7952.213719.470837@localhost.redhat.com \
    --to=ezannoni@redhat.com \
    --cc=carlton@math.stanford.edu \
    --cc=drow@mvista.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