From: Stan Shebs <stan@codesourcery.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Stan Shebs <stan@codesourcery.com>
Subject: Re: [PATCH] Whack some dead code
Date: Tue, 30 Mar 2010 17:05:00 -0000 [thread overview]
Message-ID: <4BB22F4A.1030506@codesourcery.com> (raw)
In-Reply-To: <201003301203.22533.pedro@codesourcery.com>
Pedro Alves wrote:
> On Tuesday 30 March 2010 01:25:11, Stan Shebs wrote:
>
>> A while back, Vladimir Prus noticed a chunk of dead code in
>> trace_find_line_command; basically, if you don't have symbolic info,
>> there is no plausible fallback for line numbers, you just have to give
>> up. Committed to trunk.
>>
>
>
>> * tracepoint.c (trace_find_line_command): Remove dead code.
>>
>
> Errr, what does "dead" mean exactly? It's certainly exercisable, just
> like the comment in the code suggests:
>
> (top-gdb) help tfind line
> Select a trace frame by source line.
> Argument can be a line number (with optional source file),
> a function name, or '*' followed by an address.
> Default argument is 'the next source line that was traced'.
>
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. 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. "info line" is
not necessarily the right model, since as an info command it has no side
effects and can make far-out interpretations.
(Incidentally, I notice that "help info line" doesn't mention the raw
address option. Didn't it used to??)
Stan
next prev parent reply other threads:[~2010-03-30 17:05 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 [this message]
2010-03-30 17:41 ` Pedro Alves
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=4BB22F4A.1030506@codesourcery.com \
--to=stan@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@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