On Wed, Mar 10, 2010 at 10:07 AM, John Lee wrote:

> Set easy options that apply to all handles: (NOSIGNAL, ...
> Program received signal SIGPIPE, Broken pipe.
> Any idea what I'm doing wrong and why SIGPIPE is still getting handled?

If I understand correctly, CURLOPT_NOSIGNAL prevents libcurl from
purposefully generating any signals on its own, but that doesn't
prevent the os or libc from generating signals as usual.

If you want for gdb to continue when it encounters a SIGPIPE
you can try issuing a command like:

  (gdb) handle SIGPIPE nostop pass

before running your program.

 - Jeff
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette: http://curl.haxx.se/mail/etiquette.html
Received on 2010-03-10