This is the mail archive of the
gdb@sourceware.org
mailing list for the GDB project.
Async event loop misses breakpoints
- From: Nick Roberts <nickrob at snap dot net dot nz>
- To: gdb at sources dot redhat dot com
- Date: Fri, 8 Sep 2006 12:10:47 +1200
- Subject: Async event loop misses breakpoints
I've created a test file (mi-async.exp) for my branch nickrob-async-20060513
which sometimes stops at the right places:
runtest mi-async.exp
(gdb)
start
&"start\n"
~"Breakpoint 1 at 0x804840c: file ../.././gdb/testsuite/gdb.mi/basics.c, line 54.\n"
~"Starting program: /home/nickrob/src1/gdb/testsuite/gdb.mi/basics \n"
^running
^done
(gdb)
*stopped,thread-id="0",frame={addr="0x0804840c",func="main",args=[],file="../.././gdb/testsuite/gdb.mi/basics.c",fullname="/home/nickrob/src1/gdb/testsuite/gdb.mi/basics.c",line="54"}
and sometimes doesn't:
make check RUNTESTFLAGS=mi-async.exp
(gdb)
start
&"start\n"
~"Breakpoint 1 at 0x804840c: file ../.././gdb/testsuite/gdb.mi/basics.c, line 54.\n"
~"Starting program: /home/nickrob/src1/gdb/testsuite/gdb.mi/basics \n"
^running
^done
(gdb)
Hello, World!*stopped,reason="exited-normally"
(gdb)
FAIL: gdb.mi/mi-async.exp: Asynchronous response after start command (2)
I've have run simple programs _exactly_ the same way, and again found that
sometimes it stops in main after `start' and sometimes it doesn't.
Does anyone have any ideas as to what the underlying cause of the difference
might be?
--
Nick http://www.inet.net.nz/~nickrob