Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Mark E." <snowball3@bigfoot.com>
To: gdb-patches@sources.redhat.com
Subject: [RFA] coffread.c: support dwarf2 info
Date: Sat, 23 Jun 2001 09:08:00 -0000	[thread overview]
Message-ID: <3B348696.10582.20EF43@localhost> (raw)

Hello folks,
A few months ago I successfully added coff support for dwarf2 info to 
binutils so djgpp debuggers could use it. And the new version of gcc has been 
configured to generate dwarf2 info. GDB just needs a small change to (almost) 
complete the chain.

I've altered coffread.c to read in dwarf2 info just like in elfread.c. Please 
consider commiting the following patch:

gdb/Changelog

2001-06-23  Mark Elbrecht  <snowball@bigfoot.com>

	* coffread.c (coff_symfile_read): Parse DWARF2 info if present.

*** coffread.c.orig	Tue May 29 06:45:10 2001
--- coffread.c	Fri Jun 22 17:02:56 2001
*************** coff_symfile_read (struct objfile *objfi
*** 689,694 ****
--- 689,699 ----
  			       info->stabsects,
  			       info->stabstrsect->filepos, stabstrsize);
      }
+   if (dwarf2_has_info (abfd))
+     {
+       /* DWARF 2 sections */
+       dwarf2_build_psymtabs (objfile, mainline);
+     }
  
    do_cleanups (back_to);
  }

After that, only one obstacle remains. The dwarf2 reader uses 
'bfd_get_sign_extended_vma' from the bfd library. For whatever reason, that 
function only works with the elf format. But that's not a program that you 
folks can fix since it's in the bfd library. After I hacked it to return a 
legit value, I was able to set breakpoints and step through programs 
containing dwarf2 info.

Mark


             reply	other threads:[~2001-06-23  9:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-23  9:08 Mark E. [this message]
2001-06-28  4:55 ` Eli Zaretskii
2001-06-29  5:44   ` Philippe De Muyter
2001-07-01  3:05     ` Eli Zaretskii

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=3B348696.10582.20EF43@localhost \
    --to=snowball3@bigfoot.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