From: Michael Snyder <msnyder@redhat.com>
To: Stan Shebs <shebs@apple.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA/RFC] testsuite: gdb_run_cmd tweak
Date: Mon, 18 Apr 2005 23:00:00 -0000 [thread overview]
Message-ID: <42643BED.7010509@redhat.com> (raw)
In-Reply-To: <42643016.1080802@apple.com>
Stan Shebs wrote:
> Michael Snyder wrote:
>
>> Stan Shebs wrote:
>>
>>> Michael Snyder wrote:
>>>
>>>> This just adds a regular expression to prevent gdb_run_cmd
>>>> from choking on the msg that gdb emits when it detects that
>>>> the file has changed and re-reads the symbols.
>>>>
>>>> I honestly don't remember the circumstances that caused me
>>>> to add this -- it's been sitting in my sandbox for a while.
>>>> Thought it would be better to offer it up than to throw it
>>>> away...
>>>
>>>
>>>
>>>
>>> Wouldn't a message like this be symptomatic of failure
>>> in GDB's executable date detection code, or in the executable
>>> production bits?
>>
>>
>>
>> If I understand it, we get that message precisely when
>> gdb's executable date detection code works as intended.
>> It discovers that the executable's modification date has
>> changed, and therefore re-reads the symbols.
>
>
> But when would that happen while running the testsuite?
> I would expect that the executable is left alone between run
> commands - if GDB thinks it needs to re-read symbols between
> run commands on the same executable, that seems like a GDB
> bug and a performance loss to boot.
OK, let's drop it then. As I say, I don't remember
why I did it in the first place.
next prev parent reply other threads:[~2005-04-18 23:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 19:51 Michael Snyder
2005-04-18 21:42 ` Stan Shebs
2005-04-18 21:46 ` Michael Snyder
2005-04-18 22:09 ` Stan Shebs
2005-04-18 23:00 ` Michael Snyder [this message]
2005-04-19 15:49 ` Paul Gilliam
2005-04-19 16:36 ` Daniel Jacobowitz
2005-04-18 21:54 ` Daniel Jacobowitz
2005-04-18 22:05 ` 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=42643BED.7010509@redhat.com \
--to=msnyder@redhat.com \
--cc=gdb-patches@sources.redhat.com \
--cc=shebs@apple.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