thread and gc.fullCollect

Ant duitoolkit at yahoo.ca
Thu Jan 11 17:57:29 PST 2007


Frank Benoit (keinfarbton) wrote:
> You need to configure gdb in that way it does not stop at SIGUSR1/2.
> These signals are used by the GC to pause the program.
> 
> in the GDB command line use these commands:
> handle SIGUSR1 nostop noprint
> handle SIGUSR2 nostop noprint
> 
> 
> then run the program.

ah...

so the program just prints count twice and exists normally.

is this a bug?

Ant


(gdb) handle SIGUSR1 nostop noprint
Signal        Stop      Print   Pass to program Description
SIGUSR1       No        No      Yes             User defined signal 1
(gdb) handle SIGUSR2 nostop noprint
Signal        Stop      Print   Pass to program Description
SIGUSR2       No        No      Yes             User defined signal 2
(gdb) r
Starting program: /tt
[Thread debugging using libthread_db enabled]
[New Thread -1210354000 (LWP 12324)]
[New Thread -1211405408 (LWP 12325)]
Count = 0
Count = 1
[Thread -1211405408 (LWP 12325) exited]

Program exited normally.
(gdb)


More information about the Digitalmars-d-learn mailing list