From: Pedro Alves <pedro@codesourcery.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Whack some dead code
Date: Tue, 30 Mar 2010 17:41:00 -0000 [thread overview]
Message-ID: <201003301841.21510.pedro@codesourcery.com> (raw)
In-Reply-To: <4BB22F4A.1030506@codesourcery.com>
On Tuesday 30 March 2010 18:05:14, Stan Shebs wrote:
> A better term is maybe "bogus code", and my explanation is misleading.
> If you look at the locals start_pc and end_pc, you see that the original
> code's sal.symtab == 0 case does not set them before they get passed to
> tfind_1 at the bottom. I suppose one could try to salvage the sal.pc !=
> 0 case and treat it as a start_pc == end_pc situation; we'd would want
> to think how each case is supposed to be useful.
Whoops, yeah, there was a bug here. The intention was certainly for
treating sal.pc != 0 case as start_pc == end_pc. I don't know how
useful that would be. The " for address 0x....... <functname>" part
did looks a bit useful, but I won't cry over it being gone.
> It would be a little
> annoying if a typo in tfind takes you to an unexpected trace frame,
> which in turn could disable your display commands, etc.
Well, there was an obvious bug. That remark applies to all bugs. :-)
> (Incidentally, I notice that "help info line" doesn't mention the raw
> address option. Didn't it used to??)
(Hmm. I've tried gdb 5.3 (2002), and it doesn't, the help text
looks the same. Don't have older builds handy.)
--
Pedro Alves
next prev parent reply other threads:[~2010-03-30 17:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 0:25 Stan Shebs
2010-03-30 11:03 ` Pedro Alves
2010-03-30 17:05 ` Stan Shebs
2010-03-30 17:41 ` Pedro Alves [this message]
2010-03-30 17:44 ` Michael Snyder
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=201003301841.21510.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=stan@codesourcery.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