From: "Thomas Köhler" <jean-luc@picard.franken.de>
To: zsh-workers@sunsite.auc.dk
Subject: Re: zsh-3.1.9-dev-6 crashes occassionally
Date: Wed, 8 Nov 2000 11:33:34 +0100 [thread overview]
Message-ID: <20001108113334.A6870@picard.franken.de> (raw)
In-Reply-To: <200011080941.KAA21063@beta.informatik.hu-berlin.de>; from wischnow@informatik.hu-berlin.de on Wed, Nov 08, 2000 at 10:41:41AM +0100
[-- Attachment #1: Type: text/plain, Size: 1884 bytes --]
On Wed, Nov 08, 2000 at 10:41:41AM +0100,
Sven Wischnowsky <wischnow@informatik.hu-berlin.de> wrote:
>
> Bart Schaefer wrote:
>
> > On Nov 1, 10:41am, Sven Wischnowsky wrote:
> > }
> > } Here's the second version, still not-to-be-committed.
> >
> > Of course, the question is, does this actually fix Thomas's crash?
>
> I've seen Thomas' reply.
>
> But: is this really the question? Without such a trap-handling delay
> and with the code not protecting critical code sections as it is now
> (without the patch), crashes like these can always happen. And the
> code is full of critical sections because there are many, many places
> where we access global data structures.
And lots of people will do funny things in their .zshrc and see
occassional crashes that nobody can explain. Uhm.
> However, the patch is so deep in the guts of zsh that I hesitate to
> decide if it should be committed, especially if Bart says things like
> the above ;-). I've been using it on my laptop ever since I posted it
> and didn't have any problems but I don't use TRAPALRM(), so that means
> almost nothing (but Peter and I made sure the trap-tests still work
> correctly).
Hm. Collecting patches before recompiling etc, lots of work to do before
testing. Anybody to send me a full tar-ball with this patch applied?
Perhaps I can start testing this on Saturday or such...
> Anyway, Peter has the newest version of this patch, together with his
> trap-changes.
So, if this patch will be committed, it's Peter's part to do so? :)
> Bye
> Sven
Ciao,
Thomas
--
Thomas Köhler Email: jean-luc@picard.franken.de | LCARS - Linux
<>< WWW: http://jeanluc-picard.de | for Computers
IRC: jeanluc | on All Real
PGP public key available from Homepage! | Starships
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2000-11-08 10:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-08 9:41 Sven Wischnowsky
2000-11-08 10:33 ` Thomas Köhler [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-11-08 10:54 Sven Wischnowsky
2000-11-01 9:41 Sven Wischnowsky
2000-11-03 15:42 ` Bart Schaefer
2000-11-05 17:55 ` Thomas Köhler
2000-10-31 15:42 Sven Wischnowsky
2000-10-31 13:19 Sven Wischnowsky
2000-10-31 13:51 ` Peter Stephenson
2000-10-31 14:01 ` Sven Wischnowsky
2000-10-31 15:25 ` Bart Schaefer
2000-10-31 15:43 ` Andrej Borsenkow
2000-10-30 10:25 Sven Wischnowsky
2000-10-30 8:32 Sven Wischnowsky
2000-10-30 9:56 ` Peter Stephenson
2000-10-30 10:10 ` Thomas Köhler
2000-10-30 16:18 ` Bart Schaefer
2000-10-24 7:53 Sven Wischnowsky
2000-10-23 13:04 Sven Wischnowsky
2000-10-23 15:12 ` Thomas Köhler
2000-10-21 12:34 Thomas Köhler
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=20001108113334.A6870@picard.franken.de \
--to=jean-luc@picard.franken.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).