From: Tom Tromey <tromey@redhat.com>
To: Vladimir Simonov <sv@sw.ru>
Cc: gdb-patches@sourceware.org
Subject: Re: gdb: Incorrect stack unwinding if compressed debug info is used
Date: Mon, 07 Feb 2011 15:00:00 -0000 [thread overview]
Message-ID: <m34o8f3n5m.fsf@fleche.redhat.com> (raw)
In-Reply-To: <4D4D52F2.7080802@sw.ru> (Vladimir Simonov's message of "Sat, 05 Feb 2011 16:38:58 +0300")
>>>>> "Vladimir" == Vladimir Simonov <sv@sw.ru> writes:
Vladimir> Please see attached patch. Hope it explains what I meant under
Vladimir> "change dwarf2_read_section".
Vladimir> If such changes are not acceptable by some reason(performance?,
Vladimir> readability?, something else) then I'm OK with current naming.
I'm sorry I didn't reply to that part of your message the first time.
I think the current code is a bit clearer, because seeing
"dwarf2_read_section" in a conditional seems strange, but seeing
"dwarf2_section_size" does not.
However, it is a minor point. I would probably approve either patch :-)
Vladimir> I definitely don't insist on such changes, I just interested
Vladimir> in understanding gdb "coding policy". If it is difficult
Vladimir> to explain please ignore this mail.
For something like this it is just a matter of personal taste, unless
some argument emerges to prefer one approach over the other. I think I
try to defer to other maintainers or to the original patch submitter on
matters of naming, but it is hard to say if that is what I actually do
;-)
Tom
next prev parent reply other threads:[~2011-02-07 15:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1296238472.3009.ezmlm@sourceware.org>
2011-01-31 16:57 ` Vladimir Simonov
2011-02-02 19:55 ` Paul Pluzhnikov
2011-02-03 16:51 ` Vladimir Simonov
2011-02-04 16:35 ` Tom Tromey
2011-02-04 16:34 ` Tom Tromey
2011-02-04 17:47 ` Vladimir Simonov
2011-02-04 17:56 ` Tom Tromey
2011-02-04 18:43 ` Vladimir Simonov
2011-02-04 20:31 ` Tom Tromey
2011-02-05 13:53 ` Vladimir Simonov
2011-02-07 15:00 ` Tom Tromey [this message]
2011-02-01 7:34 ` gdb: Incorrect stack unwinding if debug info is compressed Vladimir Simonov
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=m34o8f3n5m.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=sv@sw.ru \
/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