Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [Bug] ZSH segmentation fault
- X-seq: zsh-workers 23514
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [Bug] ZSH segmentation fault
- Date: Sun, 03 Jun 2007 17:55:01 -0700
- In-reply-to: <200706031736.l53HaAJI003047@xxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <200706031736.l53HaAJI003047@xxxxxxxxxxxxxxxxxxx>
On Jun 3, 6:36pm, Peter Stephenson wrote:
} Subject: Re: [Bug] ZSH segmentation fault
}
} DervishD wrote:
} > While I understand that running such scripts is very unusual, I
} > think that just segfaulting is not a correct way of dealing with errors.
}
} I didn't claim it was, indeed I think I implied the opposite.
It might suffice to have a segfault handler (possibly turned off when the
shell is compiled for debugging) which generically prints a message and
aborts cleanly rather than producing a core dump. It's the same as far
as the end result of the script is concerned, which is why we've never
bothered with it so far, but it gives the appearance that the shell knows
what it's doing when a less-sophisticated user accidentally induces a
fault.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author