Porting GDC to QNX

[Sheff]

Frits van Bommel Wrote:

> That doesn't mean the signal causes the crash. It could still be that 
> the crash is _after_ the gc run. You should try either ignoring the 
> signals or telling gdb to continue when it stops on them, to see what 
> happens afterwards.

Hm, I think that just ignoring that signal is wrong, because, for example, in linux, the same code works fine and doesn't send signals. When I continue on the signal in gdb it writes "Memory fault":

Program received signal SIGUSR1, User defined signal 1.
[Switching to process 66433068]
0xb032f092 in ThreadJoin_r () from /usr/qnx630/target/qnx6/x86/lib/libc.so.2
(gdb) bt
#0  0xb032f092 in ThreadJoin_r ()
   from /usr/qnx630/target/qnx6/x86/lib/libc.so.2
#1  0xb031a801 in pthread_join ()
   from /usr/qnx630/target/qnx6/x86/lib/libc.so.2

**Memory fault**