difference in non-stop/async behaviour, terminal vs script

[Doug Evans]

Hi.  What should the effect of this script be?

set non-stop on
set target-async on
set auto-solib-add off
break main
run
sharedlib mumble
break mumble.cc:42

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
equivalent to"run&".

btw, it seems like for scripting purposes there should be a "wait"
command (akin to "wait" in bash), for situations like "run&".

Comments?