public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Gerrit P. Haase" <freeweb@nyckelpiga.de>
To: Wolfgang Schnerring <wosc@wosc.de>
Cc: cygwin@cygwin.com
Subject: Re: WML (perl-based program) segfaults
Date: Thu, 12 Feb 2004 09:24:00 -0000	[thread overview]
Message-ID: <129240678667.20040212102414@familiehaase.de> (raw)
In-Reply-To: <20040212090742.GA1228@nautis.wosc.de>

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/

  reply	other threads:[~2004-02-12  9:24 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 [this message]
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=129240678667.20040212102414@familiehaase.de \
    --to=freeweb@nyckelpiga.de \
    --cc=cygwin@cygwin.com \
    --cc=wosc@wosc.de \
    /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).