WML (perl-based program) segfaults

WML (perl-based program) segfaults

[Wolfgang Schnerring]

Hello!

I had used WML (offline HTML generator, Perl-based, version 2.0.9,
<http://thewml.org>) happily under Cygwin with no problems whatsoever.
Then along came some system-upgrade[1], and boom, eperl (a
subcomponent of WML) just dies when trying to open a file. (That
means, e.g. "eperl --help" produces some output, so the program
doesn't *completely* just die) The other WML-components still work
just fine.

I'm no expert on debugging this kind of things, but I ./configure'd
WML with --enable-debug and was able to get this from gdb:

###
$ gdb eperl
This GDB was configured as "i686-pc-cygwin"...
Minimal symbols from eperl.exe...(no debugging symbols found)...
[I think that's strange, as I *did* say --enable-debug]

(gdb) run README
[this just proves the point that the actual file doesn't matter]

Starting program: /cygdrive/d/wosc/install/Cygwin/wml-2.0.9/wml_backend/p3_eperl/eperl.exe README

Program received signal SIGSEGV, Segmentation fault.
0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
(gdb) bt
#0  0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
#1  0x1007254c in cygperl5_8_2!Perl_sv_add_arena () from /usr/bin/cygperl5_8_2.dll
#2  0x1007dc8b in cygperl5_8_2!Perl_newSVpvn () from /usr/bin/cygperl5_8_2.dll
#3  0x10058488 in cygperl5_8_2!Perl_savesharedpv () from /usr/bin/cygperl5_8_2.dll
#4  0x100586b7 in cygperl5_8_2!Perl_vmess () from /usr/bin/cygperl5_8_2.dll
#5  0x10059171 in cygperl5_8_2!Perl_vcroak () from /usr/bin/cygperl5_8_2.dll
#6  0x1005963f in cygperl5_8_2!Perl_croak_nocontext () from /usr/bin/cygperl5_8_2.dll
[this sequence keeps repeating over and over]
###

Does anybody have an idea what I might be looking at here, and what I
could do about it?

Thanks for your help,
Wolfgang


[1] from what I know, it might have been core cygwin.dll 1.5-3 to -4
or perl-5.8.0 to -5.8.2, but that's just me guessing, because
reverting to the old versions doesn't solve the problem.
This just proves the saying "Never touch a running system"... :-(
Current Versions are cygwin-1.5.7-1 and perl-5.8.2-1.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Gerrit P. Haase]

Hallo Wolfgang,

Am Dienstag, 10. Februar 2004 um 16:26 schriebst du:

> Hello!

> I had used WML (offline HTML generator, Perl-based, version 2.0.9,
> <http://thewml.org>) happily under Cygwin with no problems whatsoever.
> Then along came some system-upgrade[1], and boom, eperl (a
> subcomponent of WML) just dies when trying to open a file. (That
> means, e.g. "eperl --help" produces some output, so the program
> doesn't *completely* just die) The other WML-components still work
> just fine.

> I'm no expert on debugging this kind of things, but I ./configure'd
> WML with --enable-debug and was able to get this from gdb:

> ###
> $ gdb eperl
> This GDB was configured as "i686-pc-cygwin"...
> Minimal symbols from eperl.exe...(no debugging symbols found)...
> [I think that's strange, as I *did* say --enable-debug]

Try also to define some debugging flags for the tools, hmmm, in the
eperl configure is already defined: CFLAGS='-g' && LDFLAGS='-g', maybe
it is neccessary to rebuild perl with symbols too?


> (gdb) run README
> [this just proves the point that the actual file doesn't matter]

> Starting program:
> /cygdrive/d/wosc/install/Cygwin/wml-2.0.9/wml_backend/p3_eperl/eperl.exe
> README

> Program received signal SIGSEGV, Segmentation fault.
> 0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
> (gdb) bt
> #0  0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
> #1  0x1007254c in cygperl5_8_2!Perl_sv_add_arena () from /usr/bin/cygperl5_8_2.dll
> #2  0x1007dc8b in cygperl5_8_2!Perl_newSVpvn () from /usr/bin/cygperl5_8_2.dll
> #3  0x10058488 in cygperl5_8_2!Perl_savesharedpv () from /usr/bin/cygperl5_8_2.dll
> #4  0x100586b7 in cygperl5_8_2!Perl_vmess () from /usr/bin/cygperl5_8_2.dll
> #5  0x10059171 in cygperl5_8_2!Perl_vcroak () from /usr/bin/cygperl5_8_2.dll
> #6  0x1005963f in cygperl5_8_2!Perl_croak_nocontext () from /usr/bin/cygperl5_8_2.dll
> [this sequence keeps repeating over and over]
> ###

> Does anybody have an idea what I might be looking at here, and what I
> could do about it?

> Thanks for your help,
> Wolfgang


> [1] from what I know, it might have been core cygwin.dll 1.5-3 to -4
> or perl-5.8.0 to -5.8.2, but that's just me guessing, because
> reverting to the old versions doesn't solve the problem.
> This just proves the saying "Never touch a running system"... :-(
> Current Versions are cygwin-1.5.7-1 and perl-5.8.2-1.

The first sentence at this website is:

"Support for Perl 5.8.0 added in WML 2.0.9"

Maybe it just won't work with perl-5.8.2 yet?

Also the configure script is kind of buggy as it doesn't find the
already installed modules:

> CHECK: Perl Language
> checking for Perl language... /bin/perl v5.008
> checking for Perl module Getopt::Long (2.16)... syntax error at -e line 1, near "require Getopt::Long 2.16"
> Execution of -e aborted due to compilation errors.
> not found

$ perl -e 'use Getopt::Long; print $Getopt::Long::VERSION;'
2.34

[...]

> checking for Perl module IO::File (1.07)... syntax error at -e line 1, near "require IO::File 1.07"
> Execution of -e aborted due to compilation errors.
> not found

$ perl -e 'use IO::File; print $IO::File::VERSION;'
1.10

> checking for Perl module Term::ReadKey (2.11)... syntax error at -e line 1, near "require Term::ReadKey 2.11"
> Execution of -e aborted due to compilation errors.
> not found

$ perl -e 'use Term::ReadKey; print $Term::ReadKey::VERSION;'
2.21

> checking for MakeMaker's private install paths... ok

1 hour later:
I'm still trying to get it configured... it is a terrible package,
I wonder that it was possible to build it under Cygwin;)

When trying to install the modules used by WML I see this:

>   CPAN.pm: Going to build R/RB/RBS/File-PathConvert-0.9.tar.gz
> 
> 
> *** THIS MODULE (File::PathConvert) IS DEPRECATED. ****
> 
> There are several known bugs, and it is not being actively
> maintained since all functionality is now available in
> modules (Cwd.pm and File::Spec) bundled in every Perl
> distribution of recent vintage.  This version is provided to
> fix a few bugs and to get the word out about the
> deprecation.
> 
> Please use Cwd::abs_path() instead of
> File::PathConvert::realpath() and File::Spec methods instead
> of all other path manipulation functions in this module.
> 
> If you use setfstype, you probably want to access a File::Spec::Foo
> module for the appropriate operating system.
> 
> There is also a version of File::Spec on CPAN for backwards
> compatability.
> 
> Thank you,
> 
> Barrie Slaymaker


Ok, now running:
./configure --with-openworld --enable-debug

and getting:
CHECK: Perl Language
checking for Perl language... /bin/perl v5.008
checking for Perl module Getopt::Long (2.16)... found
checking for Perl module Bit::Vector (5.2)... found
checking for Perl module File::PathConvert (ANY)... found
checking for Perl module Image::Size (2.6)... found
checking for Perl module IO::File (1.07)... found
checking for Perl module Term::ReadKey (2.11)... found
checking for MakeMaker's private install paths... ok

FINE;)

runing make ends here:

mp4h: ERROR: failed to initialise modules: unknown error


And running make in the eperl subdirectory gives me an
executable which shows the same symptoms as you described:

Program received signal SIGSEGV, Segmentation fault.
0x1000ad60 in cygperl5_8_2!Perl_malloc () from /bin/cygperl5_8_2.dll

Two of the executables are broken for me now, I consider to stop
working on this now.  Maybe you should ask the upstream maintainer if
it is possible to use WML with perl-5.8.2 or not.  Details about
support is in the top sourcedir SUPPORT file.


Some final words:
Most of Engelschalls software is completely out of date.

Gerrit
-- 
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Wolfgang Schnerring]

Hello!

Gerrit, thank you very much for looking into this!

* Gerrit P. Haase <gp@familiehaase.de> [2004-02-11 23:35]:
> "Support for Perl 5.8.0 added in WML 2.0.9"
> Maybe you should ask the upstream maintainer if it is possible to
> use WML with perl-5.8.2 or not.

Unfortunately, switching to perl-5.8.0-5 and rebuilding WML doesn't
make the situation any different:

$ gdb eperl.exe
(gdb) run README
Starting program:
/cygdrive/d/wosc/install/Cygwin/wml-2.0.9/wml_backend/p3_eperl/eperl.exe README

Program received signal SIGSEGV, Segmentation fault.
0x00405d66 in ?? ()
(gdb) bt
#0  0x00405d66 in ?? ()
#1  0x0022c840 in ?? ()
#2  0x0022ef4c in ?? ()
#3  0x00000800 in ?? ()
#4  0x0022da88 in ?? ()
#5  0x101233d0 in ?? ()
#6  0xffffffff in ?? ()
#7  0x0022c568 in ?? ()
#8  0x0000021a in ?? ()
#9  0x00236dd0 in ?? ()

Well, OK, it is different, but definitely not better. :-(

> I'm still trying to get it configured... it is a terrible package,
> I wonder that it was possible to build it under Cygwin;)

I fully agree, the build system does have some *bad* quirks.
I considered myself quite lucky to get it working. %-)

> ./configure --with-openworld --enable-debug
> runing make ends here:
> mp4h: ERROR: failed to initialise modules: unknown error

This can be circumvented by specifying --without-modules ... :-/

> Two of the executables are broken for me now, I consider to stop
> working on this now. 

I am very grateful that you invested your time - I was completely
stumped.

> > Minimal symbols from eperl.exe...(no debugging symbols found)...
> > [I think that's strange, as I *did* say --enable-debug]
> 
> Try also to define some debugging flags for the tools, hmmm, in the
> eperl configure is already defined: CFLAGS='-g' && LDFLAGS='-g', maybe
> it is neccessary to rebuild perl with symbols too?

Do you think the possible results warrant the effort of rebuilding
perl?
And, honestly, even if I managed to get some useful debugging output,
I'd still depend on your help - and I wouldn't want you to spend lots
of your time debugging other people's (possibly outdated) software.
It would be great if WML did work again, as I have some projects
depending on it, but it's completely up to you whether to dig any
further. 

I appreciate your help and investigations very much, thanks again. 8-)

Wolfgang

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Gerrit P. Haase]

Hello Wolfgang,

>> ./configure --with-openworld --enable-debug
>> runing make ends here:
>> mp4h: ERROR: failed to initialise modules: unknown error

> This can be circumvented by specifying --without-modules ... :-/

Ok, I'll try this.


>> Two of the executables are broken for me now, I consider to stop
>> working on this now. 

> I am very grateful that you invested your time - I was completely
> stumped.

>> > Minimal symbols from eperl.exe...(no debugging symbols found)...
>> > [I think that's strange, as I *did* say --enable-debug]
>> 
>> Try also to define some debugging flags for the tools, hmmm, in the
>> eperl configure is already defined: CFLAGS='-g' && LDFLAGS='-g', maybe
>> it is neccessary to rebuild perl with symbols too?

> Do you think the possible results warrant the effort of rebuilding
> perl?

I have a debugging version of perl online[1] (extract it from the cygwin
root, you'll need the binary and the srctree package so the debugger may
find the sources in the right place), it is not the latest release, but
since it seems to be the same problem with older perls it should be
sufficient, however it seems that the problem is with malloc() which was
changed sometimes back in Cygwin (between 1.3.x and 1.5).  There is also
an option for WML to use dmalloc[2], maybe that helps to track this down?

> And, honestly, even if I managed to get some useful debugging output,
> I'd still depend on your help - and I wouldn't want you to spend lots
> of your time debugging other people's (possibly outdated) software.
> It would be great if WML did work again, as I have some projects
> depending on it, but it's completely up to you whether to dig any
> further. 

Debugging is always useful, maybe there is a bug in perl or in cygwin
somewhere?


> I appreciate your help and investigations very much, thanks again. 8-)


[1] ftp://ftp.cpan.org/pub/CPAN/authors/id/G/GE/GERRIT/
[2] http://anfaenger.de/cygwin-1.5/dmalloc/


Gerrit
-- 
=^..^=                                     http://nyckelpiga.de/donate.html


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Wolfgang Schnerring]

* Gerrit P. Haase <freeweb@nyckelpiga.de> [2004-02-12 10:24]:
> >> ./configure --with-openworld --enable-debug
> >> runing make ends here:
> >> mp4h: ERROR: failed to initialise modules: unknown error
> > This can be circumvented by specifying --without-modules ... :-/

Forgot to say: The subcomponents (mp4h, eperl, etc.) are pretty much
independent from each other. And as it seems, only eperl broke down...

> > Do you think the possible results warrant the effort of rebuilding
> > perl?
> I have a debugging version of perl online[1] 

Now, that's good news. 8-)
I'll try this and see if I catch something.

> however it seems that the problem is with malloc() which was changed
> sometimes back in Cygwin (between 1.3.x and 1.5). There is also an
> option for WML to use dmalloc[2], maybe that helps to track this
> down?

The --with-dmalloc option also only affects mp4h, which doesn't cause
trouble at the moment. Additionally, specifying this breaks the build
for me; so I'd rather not wake any sleeping seamonsters here. %-)

Wolfgang

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Wolfgang Schnerring]

Hello!

* Gerrit P. Haase <freeweb@nyckelpiga.de> [2004-02-12 10:24]:
> I have a debugging version of perl online[1]
> (extract it from the cygwin root, you'll need the binary and the
> srctree package so the debugger may find the sources in the right
> place)

Well, my modem did it. ;-)
Now I get this:

$ gdb eperl.exe
(gdb) run README
(gdb) up
#1  0x10064727 in Perl_vmess (my_perl=0x1026fb48, pat=0x1000be0b "panic: MUTEX_LOCK", args=0x330c4) at util.c:946
946         SV *sv = mess_alloc();
(gdb) 
#2  0x10065481 in Perl_vcroak (my_perl=0x1026fb48, pat=0x1000be0b "panic: MUTEX_LOCK", args=0x330c4) at util.c:1146
1146            msv = vmess(pat, args);
(gdb) 
#3  0x10065abf in Perl_croak_nocontext (pat=0x1000be0b "panic: MUTEX_LOCK") at util.c:1216
1216        vcroak(pat, &args);
(gdb) 
#4  0x1000c13d in Perl_malloc (nbytes=1008) at malloc.c:1558
1558    }
(gdb) 
#5  0x1008072c in S_more_sv (my_perl=0x1026fb48) at sv.c:310
310             New(704,chunk,1008,char);   /* Safefree() in sv_free_arenas()     */
(gdb) 
#6  0x1008e20b in Perl_newSVpvn (my_perl=0x1026fb48, s=0x10064450 "", len=0) at sv.c:6806
6806    }
(gdb) 
#7  0x100644f8 in S_mess_alloc (my_perl=0x1026fb48) at util.c:819
819             return sv_2mortal(newSVpvn("",0));


Err. Unfortunately, I know literally nothing about gdb, malloc, or
mutex, so ... what kind of diagnosis should I try and perform? %-)

Wolfgang

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Gerrit P. Haase]

Hallo Wolfgang,

While trying to debug this, I installed the latest cygwin snapshot,
now getting a segfault in KERNEL32.DLL instead of cygperl.dll:

(gdb) run README
Starting program: /opt/wml-2.0.9/wml_backend/p3_eperl/eperl.exe README

Program received signal SIGSEGV, Segmentation fault.
0x77f1b512 in KERNEL32!IsBadWritePtr () from /c/WINNT/system32/KERNEL32.DLL
(gdb) bt
#0  0x77f1b512 in KERNEL32!IsBadWritePtr ()
   from /c/WINNT/system32/KERNEL32.DLL
#1  0x00000014 in ?? ()
#2  0x1010f7d0 in PL_curinterp ()
(gdb) 

I think I need to rebuild cygwin with debugging and also recompile
perl with symbols against the new cygwin1.dll.

Unfortunately I have not much spare time the next weeks.


Gerrit
-- 
=^..^=



--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

Re: WML (perl-based program) segfaults

[Wolfgang Schnerring]

Hello!

* Gerrit P. Haase <gp@familiehaase.de> [2004-02-14 17:21]:
> While trying to debug this, I installed the latest cygwin snapshot,
> now getting a segfault in KERNEL32.DLL instead of cygperl.dll:

It's getting better and better... :-/

> I think I need to rebuild cygwin with debugging and also recompile
> perl with symbols against the new cygwin1.dll.
> Unfortunately I have not much spare time the next weeks.

No worries - I can wait. I would be really glad if you tackled this at
some point, so ... aufgeschoben ist nicht aufgehoben. ("postponed
doesn't mean cancelled").

Thanks for your help,

Wolfgang

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

RE: WML (perl-based program) segfaults

[Rafael Kitover]

>-----Original Message-----
>From: cygwin-owner@cygwin.com [mailto:cygwin-owner@cygwin.com] On Behalf Of
>Wolfgang Schnerring
>Sent: Tuesday, February 10, 2004 7:27 AM
>To: cygwin@cygwin.com
>Subject: WML (perl-based program) segfaults
>
[SNIP]
>Starting program: /cygdrive/d/wosc/install/Cygwin/wml-
>2.0.9/wml_backend/p3_eperl/eperl.exe README
>
>Program received signal SIGSEGV, Segmentation fault.
>0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
>(gdb) bt
>#0  0x1000ad60 in cygperl5_8_2!Perl_malloc () from /usr/bin/cygperl5_8_2.dll
>#1  0x1007254c in cygperl5_8_2!Perl_sv_add_arena () from
>/usr/bin/cygperl5_8_2.dll
>#2  0x1007dc8b in cygperl5_8_2!Perl_newSVpvn () from /usr/bin/cygperl5_8_2.dll
>#3  0x10058488 in cygperl5_8_2!Perl_savesharedpv () from
>/usr/bin/cygperl5_8_2.dll
>#4  0x100586b7 in cygperl5_8_2!Perl_vmess () from /usr/bin/cygperl5_8_2.dll
>#5  0x10059171 in cygperl5_8_2!Perl_vcroak () from /usr/bin/cygperl5_8_2.dll
>#6  0x1005963f in cygperl5_8_2!Perl_croak_nocontext () from
>/usr/bin/cygperl5_8_2.dll
>[this sequence keeps repeating over and over]
>###
>
>Does anybody have an idea what I might be looking at here, and what I
>could do about it?

If this thing is mixing malloc/frees between dlls, like in a problem we saw a
few days ago, this wouldn't be surprising... If it works with 5.8.2 on linux,
then that's probably the case.

-- 
Rafael

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/