Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

use Perl Log In

Log In

[ Create a new account ]

james (1129)

james
  (email not shown publicly)
http://whoot.org/

...

Journal of james (1129)

Thursday January 30, 2003
06:24 AM

Tracking down segfaults

[ #10293 ]

A couple of us spent ages tracking down a segfault last night. This fault has been annoying us for a while, as we couldn't isolate when and where it was happening. Yesterday we found out roughly where it happened, and called the pack to chase.
After about four hours of gdb, printlines and hoping for the segfault to appear we got it. One line in the MIME::Lite module, that occasionally would cause the system to segfault:

    open SENDMAIL, "|$sendmailcmd"

Phffft. Something is going wrong in open somewhere, sometimes. Time to change the implementation methinks.

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Phffft. Something is going wrong in open somewhere, sometimes.

    Did you try running it under valgrind [kde.org] to get a backtrace of exactly where in the C source the SEGV was? If you can get a line number and argument backtrace from a -g> build that would make an interesting perl bug report.