[Bug breakpoints/16551] Execution stops when encountering a dprintf with an invalid string

["antoine.tremblay at ericsson dot com" <sourceware-bugzilla@sourceware.org>]

https://sourceware.org/bugzilla/show_bug.cgi?id=16551

--- Comment #1 from Antoine Tremblay <antoine.tremblay at ericsson dot com> ---
After some research in gdb it seems to me that the expectation is that if a
command fails gdb returns to prompt in it's current execution state.
The expectation of the developer should be that if a command input is wrong,
gdb
can't do what the user requested and control is returned to the developer
to fix the error.

This seems consistent accross all commands in gdb... I think changing that
a dprintf fails with an error to a warning and allowing the program to continue
could break this consistency and be more trouble for the developer as he won't
be given a chance to fix the issue as soon as possible during his debugging
session. He would have to wait until the end of the execution. 

Also, the fact that he called exec-run only gives the developer the expectation
that gdb will continue until it reaches a breakpoint, and a dprintf is
consired a breakpoint in that sense, so it should not be unexpected
for the developer that dprintf can stop the execution in case of failure.

I'm also uncertain about what you mean by the stopped event beeing missed ?

As dprintf is called by a stop event...

Also bug 15185 would not fix the isssue since we can only know about the bad 
symbol at the runtime of that line since shared libraries could be loaded
dynamicaly thus we can't prevalidate the dprintf input as we enter it.

-- 
You are receiving this mail because:
You are on the CC list for the bug.