From: "H. J. Lu" <hjl@lucon.org>
To: binutils@sources.redhat.com
Subject: Re: PATCH: Modify .debug_loc output from readelf
Date: Sat, 26 Feb 2005 11:48:00 -0000 [thread overview]
Message-ID: <20050225221057.GA9316@lucon.org> (raw)
In-Reply-To: <20050218025756.GA13605@lucon.org>
On Thu, Feb 17, 2005 at 06:57:56PM -0800, H. J. Lu wrote:
> We output:
>
> Contents of the .debug_loc section:
>
> Offset Begin End Expression
> <End of list>
> 00000014 00000000 00000004 (DW_OP_fbreg: 4)
> 00000014 00000004 00000028 (DW_OP_reg2)
> <End of list>
> 00000033 0000002a 0000002a (DW_OP_breg4: -1) (start == end)
> <End of list>
>
> This patch changes it to
>
> Offset Begin End Expression
> 00000000 <End of list>
> 00000014 00000000 00000004 (DW_OP_fbreg: 4)
> 00000014 00000004 00000028 (DW_OP_reg2)
> 00000014 <End of list>
> 00000033 0000002a 0000002a (DW_OP_breg4: -1) (start == end)
> 00000033 <End of list>
>
> It is clearer.
>
>
> H.J.
> ----
> 2005-02-17 H.J. Lu <hongjiu.lu@intel.com>
>
> * readelf.c (display_debug_loc): Print out offset for end of
> list.
>
display_debug_ranges has the same problem. I will check in this one
as an obvious fix.
H.J.
---
2005-02-25 H.J. Lu <hongjiu.lu@intel.com>
* readelf.c (display_debug_ranges): Print out offset for end of
list.
--- binutils/readelf.c.addr 2005-02-25 12:14:14.304752738 -0800
+++ binutils/readelf.c 2005-02-25 13:32:12.288017680 -0800
@@ -9837,7 +9837,10 @@ display_debug_ranges (Elf_Internal_Shdr
start += pointer_size;
if (begin == 0 && end == 0)
- break;
+ {
+ printf (_(" %8.8lx <End of list>\n"), offset);
+ break;
+ }
/* Check base address specifiers. */
if (begin == -1UL && end != -1UL)
@@ -9858,7 +9861,6 @@ display_debug_ranges (Elf_Internal_Shdr
putchar ('\n');
}
- fputs (_(" <End of list>\n"), stdout);
}
}
putchar ('\n');
prev parent reply other threads:[~2005-02-25 22:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 13:47 H. J. Lu
2005-02-18 19:52 ` Nick Clifton
2005-02-26 11:48 ` H. J. Lu [this message]
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=20050225221057.GA9316@lucon.org \
--to=hjl@lucon.org \
--cc=binutils@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).