comment on

This thread reminded me of an old node about debugging and the use of debuggers. And I can only dream of a shred of the skills of some mo nk s in that thread.

About your problem: perhaps it has little to do with your code or the library you are working with. Are you interested in the system you find the segfault with, i.e. is it important to you? Perhaps it is a heavily patched, manual installation as opposed to a freshly installed popular distribution. Perhaps you cannot even repeat the segfault with the same distribution on slightly different hardware.

Hope this helps,
Jeroen

"We are not alone"(FZ)

In reply to Re: GDB journey into perl internals by jeroenes
in thread GDB journey into perl internals by cosimo

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


There's more than one way to do things
	PerlMonks