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
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 st
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, cur
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 corrupti
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.
#0 Perl_croak (pat=0xae7ca0 "Assertion ((sv)->sv_flags &
(0x2000|0x4000|0x8000)) failed: file \"%s\", line %d"
Getting some weird coredumps, recompile with debugging, and breakpoint
on Perl_croak gave me this.
#0 Perl_croak (pat=0xae7ca0 "Assertion ((sv)->sv_flags &
(0x2000|0x4000|0x8000)) failed: file \"%s\", line %d") at
util.c:1349
#1 0x00a0176c in S_save_magic (mgs_ix=20, sv=0x50d7dc
Getting some weird coredumps, recompile with debugging, and breakpoint
on Perl_croak gave me this.
#0 Perl_croak (pat=0xae7ca0 "Assertion ((sv)->sv_flags &
(0x2000|0x4000|0x8000)) failed: file \"%s\", line %d") at
util.c:1349
#1 0x00a0176c in S_save_magic (mgs_ix=20, sv=0x50d7dc
