No. But after doing so, still no joy. It appears to follow the first
>> I was able load and run the script under gdb as stated in . I set a
>> BP on the function of interest. gdb responded as expected with a file
>> and line number (which were correct).
>> However, when I run the script, the BP is never hit. I do see the
>> results of the failed test, so I know the function where the BP was
>> set executed.
>> Is there anything special for debugging under gdb and the script wrapper?
> Did you tell GDB to follow child processes?
> (gdb)set follow-fork-mode child
child (alloc in the tests), but no others.
Jose and me tried on weekend to run under GDB all torture tests, playing with "follow-fork-mode" and "detach-on-fork" options; but no success.
* If "set follow-fork-mode child", only the first forked child will run under GDB, and parent is "detached" from GDB, so no other new forks will get run under GDB as parent itself is not run under GDB.
* If "set follow-fork-mode child" AND "set detach-on-fork off", then both parent and child are run under GDB: the first child is executed under GDB properly, and the parent gets 'on hold'. After the first child finishes its execution under GDB, you then need to change to the on-hold parent process, which is an "inferior" in GDB (see http://sources.redhat.com/gdb/current/onlinedocs/gdb.html#Inferiors-and-Programs
), and tell it to continue execution. Once parent continues, next test case will get forked again under GDB, and you need to repeat the whole process. Thus, this is not a good method to follow if you want to debug test #300, as you may need to do it 300 times.
Then, the best way to try to debug all these tests under GDB, is to avoid forking in Check, setting the CK_FORK env variable as this, before running GDB:
$> export CK_FORK=no