From: Sven Wischnowsky <wischnow@informatik.hu-berlin.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: Curent CVS crash on Cygwin
Date: Thu, 25 Jan 2001 10:19:12 +0100 (MET) [thread overview]
Message-ID: <200101250919.KAA19039@beta.informatik.hu-berlin.de> (raw)
In-Reply-To: "Andrej Borsenkow"'s message of Thu, 25 Jan 2001 12:11:25 +0300
Andrej Borsenkow wrote:
> I got around to checking if zsh still runs on Cygwin. Looks, like no more :)
> It outputs prompt and immediately crashes after I press RETURN (or any key for
> that matter). It crashes with and without -f. I'm still struggling with this
> gdb GUI, but stack trace is:
>
> ...
>
> specifically it is a line with queue_signals()
>
> I completely missed all this discussion about signal queuing - Sven, where is
> the next place to look?
It's a macro in signals.h.
Erm, I forgot to add the `mod_export's to the signal-queue-variables.
Does this patch fix it?
Bye
Sven
Index: Src/signals.c
===================================================================
RCS file: /cvsroot/zsh/zsh/Src/signals.c,v
retrieving revision 1.14
diff -u -r1.14 signals.c
--- Src/signals.c 2001/01/16 13:44:20 1.14
+++ Src/signals.c 2001/01/25 09:18:49
@@ -44,11 +44,11 @@
/* Variables used by signal queueing */
/**/
-int queueing_enabled, queue_front, queue_rear;
+mod_export int queueing_enabled, queue_front, queue_rear;
/**/
-int signal_queue[MAX_QUEUE_SIZE];
+mod_export int signal_queue[MAX_QUEUE_SIZE];
/**/
-sigset_t signal_mask_queue[MAX_QUEUE_SIZE];
+mod_export sigset_t signal_mask_queue[MAX_QUEUE_SIZE];
/* This is only used on machines that don't understand signal sets. *
* On SYSV machines this will represent the signals that are blocked *
--
Sven Wischnowsky wischnow@informatik.hu-berlin.de
next reply other threads:[~2001-01-25 9:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-25 9:19 Sven Wischnowsky [this message]
2001-01-25 9:48 ` Andrej Borsenkow
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 9:11 Andrej Borsenkow
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=200101250919.KAA19039@beta.informatik.hu-berlin.de \
--to=wischnow@informatik.hu-berlin.de \
--cc=zsh-workers@sunsite.auc.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).