From: Wolfgang Schnerring <wosc@wosc.de>
To: cygwin@cygwin.com
Subject: Re: WML (perl-based program) segfaults
Date: Thu, 12 Feb 2004 10:00:00 -0000 [thread overview]
Message-ID: <20040212100113.GD1228@nautis.wosc.de> (raw)
In-Reply-To: <129240678667.20040212102414@familiehaase.de>
* 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/
next prev parent reply other threads:[~2004-02-12 10:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-10 16:03 Wolfgang Schnerring
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 [this message]
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=20040212100113.GD1228@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).