Well from my initial glance at it the segfault happens entirely in
"perl-space" - I kind of expected it to be in libxml or something. So
it looks like you've uncovered a perl bug of some sort :-(
On 1-Dec-06, at 5:01 AM, [EMAIL PROTECTED] wrote:
Obviously, when I said I had fixed it, I was mistaken.
The location / stops the seg faults etc, but then stops my other
locations from working. Which is a Bad Thing and definitely not what
I wanted :)
On 29 Nov 2006 at 12:41, Also Sprach Matt Sergeant:
On 28-Nov-06, at 5:29 AM, [EMAIL PROTECTED] wrote:
Can you run it under gdb and get a stack trace?
How do I do that?
In the axkit2 dir, run:
$ gdb perl
gdb> run ./axkit (and any flags you use here)
Then do your thing that causes the segfault. It should stop the
debugger, then type:
gdb> bt
And email back the stack trace that gives.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
