On onsdag, feb 12, 2003, at 23:31 Europe/Stockholm, Stas Bekman wrote:

A.Bergman wrote:
On onsdag, feb 12, 2003, at 00:57 Europe/Stockholm, Stas Bekman wrote:
A.Bergman wrote:

On fredag, feb 7, 2003, at 01:13 Europe/Stockholm, A. Bergman wrote:

Getting some weird coredumps, recompile with debugging, and breakpoint on Perl_croak gave me this.

[...]

That stack trace is bogus, current theory is that when perl loads a xs module there is stack corruption, the backtrace from GDB is wildly incorrect!

If earlier versions don't have this problem, perhaps Andreas' binary search can help to trace what change has caused this?
Andreas stores a lot of precompiled perls which makes his binary search quite a bit faster, I only have a 400mhz laptop so I think binary searching might take far too long time.
I see. when do you get the coredumps? During the test suite? Is manual stepping through an option?

I don't know where I get them :), yes after I submit my proposals to OSCON will do manual stepping.

Arthur



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to