This is the mail archive of the
mailing list for the GDB project.
difference in non-stop/async behaviour, terminal vs script
- From: Doug Evans <dje at google dot com>
- To: gdb <gdb at sourceware dot org>
- Date: Wed, 21 Jan 2009 23:50:48 -0800
- Subject: difference in non-stop/async behaviour, terminal vs script
Hi. What should the effect of this script be?
set non-stop on
set target-async on
set auto-solib-add off
In cvs head the part of the script after "run" is executed _before_
the program stops at main, whereas if you type that in at the keyboard
things work as expected: sharedlib/break are executed _after_ the
program stops at main. It's like "run" appearing in scripts is
btw, it seems like for scripting purposes there should be a "wait"
command (akin to "wait" in bash), for situations like "run&".