From: Paul Pluzhnikov <ppluzhnikov@google.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
gdb-patches ml <gdb-patches@sourceware.org>,
Doug Evans <dje@google.com>
Subject: Re: [patch] Re: Advice on fixing gdb/12528
Date: Wed, 16 Mar 2011 17:43:00 -0000 [thread overview]
Message-ID: <AANLkTin3DTsSgLfyTjA8CYw7oGyRc=pMc4_P_DBYq+NC@mail.gmail.com> (raw)
In-Reply-To: <20110316060658.GA10163@host1.jankratochvil.net>
On Tue, Mar 15, 2011 at 11:06 PM, Jan Kratochvil
<jan.kratochvil@redhat.com> wrote:
>> Maybe like this:
>>
>> if (address == 0 && !dwarf2_per_objfile->has_section_at_zero)
>> {
>> /* This line table is for a function which has been
>> GCd by the linker. Ignore it. PR gdb/12528 */
>>
>> long line_offset
>> = line_ptr - bytes_read - dwarf2_per_objfile->line.buffer;
>>
>> complaint (&symfile_complaints,
>> _(".debug_line offset 0x%lx uses address 0 "
>> "[in module %s]"),
>> line_offset, cu->objfile->name);
>> p_record_line = noop_record_line;
>> }
>
> BYTES_READ is here just for the ADDRESS size.
Right. So the offset printed above is the offset of the address itself.
> I do not think the displayed offset is so importatnt but at least the module
> gets shown.
I think it's still (slightly) better to print offset to the start of address,
rather than just after it.
How about this then:
if (address == 0 && !dwarf2_per_objfile->has_section_at_zero)
{
/* This line table is for a function which has been
GCd by the linker. Ignore it. PR gdb/12528 */
long line_offset
= line_ptr - bytes_read - dwarf2_per_objfile->line.buffer;
complaint (&symfile_complaints,
_(".debug_line address at offset 0x%lx is 0 "
"[in module %s]"),
line_offset, cu->objfile->name);
p_record_line = noop_record_line;
}
Thanks,
--
Paul Pluzhnikov
next prev parent reply other threads:[~2011-03-16 17:32 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-11 17:09 Paul Pluzhnikov
2011-03-11 18:27 ` Tom Tromey
2011-03-14 21:16 ` [patch] " Paul Pluzhnikov
2011-03-15 3:16 ` Jan Kratochvil
2011-03-15 5:26 ` Paul Pluzhnikov
2011-03-15 15:35 ` Tom Tromey
2011-03-15 15:45 ` Jan Kratochvil
2011-03-15 16:00 ` Paul Pluzhnikov
2011-03-15 18:50 ` Jan Kratochvil
2011-03-15 19:12 ` Paul Pluzhnikov
2011-03-15 19:18 ` Jan Kratochvil
2011-03-15 19:41 ` Paul Pluzhnikov
2011-03-15 23:26 ` Jan Kratochvil
2011-03-16 0:13 ` Paul Pluzhnikov
2011-03-16 8:20 ` Jan Kratochvil
2011-03-16 17:43 ` Paul Pluzhnikov [this message]
2011-03-16 17:52 ` Jan Kratochvil
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='AANLkTin3DTsSgLfyTjA8CYw7oGyRc=pMc4_P_DBYq+NC@mail.gmail.com' \
--to=ppluzhnikov@google.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@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