From: "Andrej Borsenkow" <Andrej.Borsenkow@mow.siemens.ru>
To: "ZSH Workers Mailing List" <zsh-workers@sunsite.dk>
Subject: General unqueue_signal problem
Date: Wed, 13 Jun 2001 10:34:14 +0400 [thread overview]
Message-ID: <000401c0f3d2$dd2dc560$21c9ca95@mow.siemens.ru> (raw)
In-Reply-To: <3B265853.3000108@mow.siemens.ru>
> cc -qlanglvl=ansi -s -o zftp.so -bI:../../Src/zsh.export
> -bE:zftp.export -emodentry zftp..o ../../Src/modentry..o -ldl -lcurses
> -lm -lc
> ld: 0711-317 ERROR: Undefined symbol: .handler
This comes from unqueue_signals() macro. This macro directly calls handler()
from signals.c (at least, I presume it is this one). But as I understand,
zftp.c sometimes install its own handler. Any other module may possible
install own handler as well.
I do not understand how signal queuing works - anybody cares to check it? It
is trivial to add mod_export to handler deinition - but I do not like it. At
least, we should change the name then. handler is too cute for a globally
visible function.
-andrej
next prev parent reply other threads:[~2001-06-13 6:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.SV4.4.33.0106120954500.24714-200000@itsrm2.mow.siemens.ru>
[not found] ` <yeh3d95lsa0.fsf@water.cs.brown.edu>
2001-06-12 17:58 ` AIX-problem: the main module won't link statically Andrej Borsenkow
2001-06-12 18:19 ` Peter Stephenson
2001-06-12 19:14 ` Bart Schaefer
2001-06-12 20:09 ` Wayne Davison
2001-06-13 9:20 ` Peter Stephenson
2001-06-13 6:09 ` 4.0.2 patches " Andrej Borsenkow
2001-06-13 9:22 ` Peter Stephenson
2001-06-13 8:46 ` Sven Wischnowsky
2001-06-13 8:48 ` Sven Wischnowsky
2001-06-13 6:34 ` Andrej Borsenkow [this message]
2001-06-13 9:30 ` General unqueue_signal problem Peter Stephenson
2001-06-18 7:21 ` Sven Wischnowsky
2001-06-18 9:20 ` Peter Stephenson
2001-06-13 10:57 ` Bart Schaefer
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='000401c0f3d2$dd2dc560$21c9ca95@mow.siemens.ru' \
--to=andrej.borsenkow@mow.siemens.ru \
--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).