This is the mail archive of the
gdb-patches@sources.redhat.com
mailing list for the GDB project.
Re: [RFA/RFC] testsuite: gdb_run_cmd tweak
- From: Michael Snyder <msnyder at redhat dot com>
- To: Stan Shebs <shebs at apple dot com>
- Cc: gdb-patches at sources dot redhat dot com
- Date: Mon, 18 Apr 2005 14:46:29 -0700
- Subject: Re: [RFA/RFC] testsuite: gdb_run_cmd tweak
- Organization: Red Hat, Inc.
- References: <42640FA7.9090406@redhat.com> <426429B8.50701@apple.com>
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.
> I think we'd only want this suppression
if the situation were explicitly known to be unavoidable,
like an outside compiler we couldn't control, or a known
OS bug, and even then we'd want to conditionalize on config.
Stan