From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.dk
Subject: Re: compilation issues
Date: Wed, 23 May 2001 15:15:37 +0200 (MET DST) [thread overview]
Message-ID: <200105231315.PAA32746@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: <Tc0a88d0153b1b5a119@mailsweeper01.cambridgesiliconradio.com>
Peter Stephenson wrote:
> Oliver Kiddle wrote:
> > alpha Compaq Tru64 5.1
> >
> > It was this machine where I got the V01zmodload test seg fault so it
> > isn't just Solaris and Cygwin.
>
> This sounds like it needs something added in Etc/MACHINES.
Hm, I'm working on a Tru64 box. V01 ends for me with a core dump, too
(from a floating point exception). And before that I get lots of
`Unresolved symbol ...' from the loader. Something I haven't seen before
and which doesn't happen with that version in normal work.
Hm, it happens at the unload for me, too. The messages about the
unresolved symbols are ok, because the last-but-one test removes all
dependencies, so zmodload thinks it can unload all modules and it's just
that the loader here is clever enough to tell us that some modules have
problems after other modules they really depend upon have been unloaded.
If I try to do at least some of the steps from the test by hand, I don't
get the floating point exception. Looking at the core dump: this seems
to have to do with the zprof module (that seems to make sense, there are
functions running and zprof hooks into the function calling code, but
that should be taken care of (delayed unloading)). And even if I wrap
some functions around the calls to zmodload I don't get the exception.
Dunno what to do now.
The other tests using modules work fine.
Bye
Sven
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next prev parent reply other threads:[~2001-05-23 13:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-23 9:06 Oliver Kiddle
2001-05-23 9:32 ` Andrej Borsenkow
2001-05-23 9:55 ` Peter Stephenson
2001-05-23 13:15 ` Sven Wischnowsky [this message]
2001-05-23 15:10 ` Oliver Kiddle
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=200105231315.PAA32746@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.dk \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).