yes, but it lacked details (since it was built optimized) and didn't show much local variables making it hard to figure out exactly why it crashed. Or can you please point out which (flawed) logic it was that made it crash?

---
** [bugs:#1383] Segmentation fault in dprintf_formatf: Lot of the curl tests are crashing with SIGSEGV.**
**Status:** open
**Created:** Wed Jun 25, 2014 07:36 AM UTC by VVPrasad
**Last Updated:** Sat Jun 28, 2014 03:23 AM UTC
**Owner:** Daniel Stenberg
Segmentation fault in dprintf_formatf: Lot of the curl tests are crashing with SIGSEGV.
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 4156541232 (LWP 13301)]
0xf7d4f722 in dprintf_formatf (data=0xf7d19580, stream=0xf7c59300 <fputc>, format=0xf7d80504 "\r%3ld %s  %3ld %s  %3ld %s  %s  %s %s %s %s %s",
    ap_save=0xff9be1c8 "d") at mprintf.c:808
808     mprintf.c: No such file or directory.
        in mprintf.c
Please have a look at the stack back trace attached for more details.
---
Sent from sourceforge.net because curl-tracker@cool.haxx.se is subscribed to https://sourceforge.net/p/curl/bugs/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/curl/admin/bugs/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.