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.