From: Wolfgang Schnerring <wosc@wosc.de>
To: cygwin@cygwin.com
Subject: WML (perl-based program) segfaults
Date: Tue, 10 Feb 2004 16:03:00 -0000 [thread overview]
Message-ID: <u4qtzklaw.fsf@nautis.wosc.de> (raw)
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/
next reply other threads:[~2004-02-10 16:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 16:03 Wolfgang Schnerring [this message]
2004-02-11 22:35 ` Gerrit P. Haase
2004-02-12 9:06 ` Wolfgang Schnerring
2004-02-12 9:24 ` Gerrit P. Haase
2004-02-12 10:00 ` Wolfgang Schnerring
2004-02-12 14:45 ` Wolfgang Schnerring
2004-02-14 16:30 ` Gerrit P. Haase
2004-02-15 7:06 ` Wolfgang Schnerring
2004-02-20 12:50 ` Rafael Kitover
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=u4qtzklaw.fsf@nautis.wosc.de \
--to=wosc@wosc.de \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).