From: Mark Kettenis <mark.kettenis@xs4all.nl>
To: jimb@red-bean.com
Cc: gdb-patches@sourceware.org
Subject: Re: [RFC/RFA] Deal with -g1 generated DWARF2 debug info
Date: Mon, 05 Dec 2005 09:43:00 -0000 [thread overview]
Message-ID: <200512042205.jB4M5GKD015863@elgar.sibelius.xs4all.nl> (raw)
In-Reply-To: <8f2776cb0512041312o19d356amabe6f7a2f47c67f1@mail.gmail.com> (message from Jim Blandy on Sun, 4 Dec 2005 13:12:41 -0800)
> Date: Sun, 4 Dec 2005 13:12:41 -0800
> From: Jim Blandy <jimb@red-bean.com>
>
> On 12/4/05, Mark Kettenis <mark.kettenis@xs4all.nl> wrote:
> > a void function. Indeed the debug info generated by -g1 for malloc
> > looks like:
> >
> > $ readelf -wi /usr/lib/libc.so.38.4:
> > ...
> > <1><af59>: Abbrev Number: 2 (DW_TAG_subprogram)
> > DW_AT_name : (indirect string, offset: 0x6484): imalloc
> > DW_AT_decl_file : 1
> > DW_AT_decl_line : 1123
> > DW_AT_low_pc : 0x67ca0
> > DW_AT_high_pc : 0x67d9f
> > DW_AT_frame_base : 1 byte block: 57 (DW_OP_reg7)
> > ...
>
> That says "imalloc"; is that really what you meant to quote?
Oops sorry, the entry for malloc isn't really different though:
<1><afc1>: Abbrev Number: 3 (DW_TAG_subprogram)
DW_AT_external : 1
DW_AT_name : (indirect string, offset: 0x6485): malloc
DW_AT_decl_file : 1
DW_AT_decl_line : 1762
DW_AT_low_pc : 0x68250
DW_AT_high_pc : 0x682ff
DW_AT_frame_base : 1 byte block: 57 (DW_OP_reg7)
Mark
next prev parent reply other threads:[~2005-12-04 22:05 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-04 22:05 Mark Kettenis
2005-12-04 22:31 ` Jim Blandy
2005-12-05 9:43 ` Mark Kettenis [this message]
2005-12-04 22:40 ` Jim Blandy
2005-12-04 23:06 ` Daniel Jacobowitz
2005-12-04 23:07 ` Jim Blandy
2005-12-05 10:32 ` Daniel Jacobowitz
2005-12-05 18:29 ` Mark Kettenis
2005-12-05 19:23 ` Daniel Jacobowitz
2005-12-07 16:19 ` Mark Kettenis
2005-12-05 16:56 ` Mark Kettenis
2005-12-05 19:57 ` Daniel Jacobowitz
2005-12-05 14:40 ` Mark Kettenis
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=200512042205.jB4M5GKD015863@elgar.sibelius.xs4all.nl \
--to=mark.kettenis@xs4all.nl \
--cc=gdb-patches@sourceware.org \
--cc=jimb@red-bean.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