This is the mail archive of the gdb@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Continue does not continue all threads in all-stop mode


I am running a head version of GDB (couple of weeks old) and noticed that
in all-stop mode with multiple inferiors continue command does not continue
all threads (all threads are processes created by fork(0). Only the current
thread is being run.

For example here is what I have:

info thread
  5 UPC Thread 3  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
  4 UPC Thread 2  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
  3 UPC Thread 1  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
* 2 UPC Thread 0  *upc_main (argc=1, argv=0x7fffffffe0a8) at src/cgB.upc:137
(gdb) c&
Continuing.
(gdb)

 Size:      14000
 Iterations:    15
info threads
  5 UPC Thread 3  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
  4 UPC Thread 2  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
  3 UPC Thread 1  *upc_main (argc=1, argv=0x7fffffffe0a8) at
src/cgB.upc:137
* 2 UPC Thread 0  (running)
(gdb)

Is this normal or an oversight?

Nenad


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]