zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: probably nothing 'segmentation fault'
Date: Tue, 27 Jan 2015 17:52:39 +0000	[thread overview]
Message-ID: <20150127175239.38ca74d0@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <54C7C73E.3090909@eastlink.ca>

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.

You need to say something like:

- I was using geany, a programme which does x and which runs zsh as a
subprocess to do y.

- At the time of the crash zsh was [sitting idle at the editing command
line at a guess?  The less I have to guess the better.]

- I issued the following command / picked the following menu item ....
blah ...

- This caused zsh to crash or misbehave.

We might *still* not be able to do anything about it, but it now
contains at least the basis of a bug report.

Hope this is useful.

pws


  reply	other threads:[~2015-01-27 17:52 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 [this message]
2015-01-27 18:13         ` Ray Andrews

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=20150127175239.38ca74d0@pwslap01u.europe.root.pri \
    --to=p.stephenson@samsung.com \
    --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).