public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Andris Pavenis <pavenis@lanet.lv>
To: "Mark E." <snowball3@bigfoot.com>
Cc: djgpp-workers@delorie.com, binutils@sources.redhat.com
Subject: Re: rhgdb and dwarf2 oddity
Date: Wed, 22 Aug 2001 04:18:00 -0000	[thread overview]
Message-ID: <Pine.A41.4.05.10108221359310.46608-100000@ieva06.lanet.lv> (raw)
In-Reply-To: <3B82C0E4.31510.103144@localhost>

On Tue, 21 Aug 2001, Mark E. wrote:

> Hi all,
> 
> You can finally debug programs using dwarf2 with rhgdb/rhide after applying 
> the dwarf2 section alignment fixes for binutils I posted to the binutils 
> list. 
> 
> I've found an anomaly debugging dwarf2 with rhgdb (didn't test rhide). When I 
> set a breakpoint at a line with dwarf2 info, rhgbd sets the breakpoint 
> without complaint. Quit rhgdb and then run it again with the same program. 
> This time rhgdb complains the breakpoint just set is invalid. But running the 
> program with Run | Run generates no complaint like an invalid breakpoint 
> would, and the program does stop at the breakpoint.
> 

Had to add missing comma to build binutils. No real testing yet
though

Andris
 
--- src/bfd/coff-stgo32.c~1     Wed Aug 22 02:00:48 2001
+++ src/bfd/coff-stgo32.c       Wed Aug 22 14:02:01 2001
@@ -49,7 +49,7 @@
 { COFF_SECTION_NAME_EXACT_MATCH (".text"), \
   COFF_ALIGNMENT_FIELD_EMPTY, COFF_ALIGNMENT_FIELD_EMPTY, 4 }, \
 { COFF_SECTION_NAME_PARTIAL_MATCH (".debug"), \
-  COFF_ALIGNMENT_FIELD_EMPTY, COFF_ALIGNMENT_FIELD_EMPTY, 0 } \
+  COFF_ALIGNMENT_FIELD_EMPTY, COFF_ALIGNMENT_FIELD_EMPTY, 0 }, \
 { COFF_SECTION_NAME_PARTIAL_MATCH (".gnu.linkonce.wi"), \
   COFF_ALIGNMENT_FIELD_EMPTY, COFF_ALIGNMENT_FIELD_EMPTY, 0 }


           reply	other threads:[~2001-08-22  4:18 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <3B82C0E4.31510.103144@localhost>]

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=Pine.A41.4.05.10108221359310.46608-100000@ieva06.lanet.lv \
    --to=pavenis@lanet.lv \
    --cc=binutils@sources.redhat.com \
    --cc=djgpp-workers@delorie.com \
    --cc=snowball3@bigfoot.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).