I'm little bit confused why my PB-debugger did not tell me anything usefull regarding SIGPIPE. It seems SIGPIPE is very deadly to my undebugged binary ... but the debugger does not really care regarding it.
I'm currently coding on a gnutls server/client application. I had a strange problem with the gnutls_bye function that caused my server to quit for mysterical reason while running without PB-debugger. Running the same with debugger in PB does not stop the process.
Finaly, running my compiled binary through gdb gave me a clue that I got a SIGPIPE after my gnutls_bye was called (that so far I understand right, should tell me that my network socket that is linked with my tls session is dead). At this point I don't really care regarding the connection via tls and the socket anyway (cause everything should clean up an die already) ... so I was able to create a sollution via adding "signal_(13,@do_nothing())" that had to be placed into the thread that called gnutls_bye.
Greetings,
auser