From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-workers@zsh.org
Subject: Re: probably nothing 'segmentation fault'
Date: Tue, 27 Jan 2015 10:13:18 -0800 [thread overview]
Message-ID: <54C7D53E.7080709@eastlink.ca> (raw)
In-Reply-To: <20150127175239.38ca74d0@pwslap01u.europe.root.pri>
On 01/27/2015 09:52 AM, Peter Stephenson wrote:
> On Tue, 27 Jan 2015 09:13:34 -0800
> Ray Andrews <rayandrews@eastlink.ca> wrote:
>> I got a seg fault that crashed geany, but it was while hot swapping the
>> working font which I was in the process of editing, so it's hardly
>> surprising that geany crashed, tho I'd not expect it's zsh's fault.
> Feel free of course to report potential bugs, but if you do you need to
> supply at least basic context information about what you were doing.
> All we know is that you were using something or other called geany.
> There is an implication here it has something to do with zsh but I don't
> know what.
Sorry Peter, I'm so sure it's not zsh's fault that I'm mentioning it in
passing just in case anyone shows the slightest interest, at which point
details would follow. It is just remotely possible that someone would
say "zsh shouldn't be reporting a seg fault due to some other program
crashing, tell us more." But you can hardly edit a working font under a
running program without that causing trouble so I spare the details.
Probably shouldn't have posted that at all. However it is the first time
I've ever seen a seg fault that wasn't due to my own tinkering. Things
crash, but zsh has never had anything to say about it before this.
geany is a quite nice GUI IDE/editor.
prev parent reply other threads:[~2015-01-27 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-26 0:20 Partial implementation of "nameref", sort of Bart Schaefer
2015-01-26 22:05 ` Oliver Kiddle
2015-01-27 16:24 ` Bart Schaefer
2015-01-27 17:13 ` probably nothing 'segmentation fault' Ray Andrews
2015-01-27 17:52 ` Peter Stephenson
2015-01-27 18:13 ` Ray Andrews [this message]
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=54C7D53E.7080709@eastlink.ca \
--to=rayandrews@eastlink.ca \
--cc=zsh-workers@zsh.org \
/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).