zsh-workers
 help / color / mirror / code / Atom feed
From: Robin Lee Powell <rlpowell@digitalkingdom.org>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>
Cc: zsh-workers@sunsite.dk, 439425-forwarded@bugs.debian.org
Subject: Re: Bug#439425: Random, but fairly regular, zsh segfaults
Date: Sat, 25 Aug 2007 10:54:22 -0700	[thread overview]
Message-ID: <20070825175422.GC4335@digitalkingdom.org> (raw)
In-Reply-To: <200708251750.l7PHoCTD003747@pws-pc.ntlworld.com>

On Sat, Aug 25, 2007 at 06:50:12PM +0100, Peter Stephenson wrote:
> Clint Adams wrote:
> > On Fri, Aug 24, 2007 at 05:40:26PM -0700, Robin Lee Powell
> > wrote:
> > > zsh does the following to me fairly regularily; this seems
> > > different to me than the other segfault bug reports.  It seems
> > > to do it slightly more often in my root shells.  It seems to
> > > motly occur when I'm typing ahead (due to engaging in
> > > complicated history searching or whatever during machine
> > > slowdowns).
> > > 
> > > I'm not sure how to get further data on this; it's pretty
> > > random. I'd be happy to work with the maintainer or upstream
> > > people, but note that I'm AFK from 28 Aug 2007 to 11 Sep 2007.
> > 
> > What are your history-related options?  What are the values of
> > $HISTSIZE and $SAVEHIST ?
> 
> It would be good to get a backtrace with full debugging
> information (configure with --enable-zsh-debug; it shouldn't make
> any difference to normal use), also to know how you're invoking
> the history search mechanism (there are lots of ways in).

Recompiling zsh will have to wait until I'm back from Japan; sorry.
I use "bindkey -v", and the most common ways I get to the history
are ESC-k and ESC-/

-Robin

-- 
http://www.digitalkingdom.org/~rlpowell/ *** http://www.lojban.org/
Reason #237 To Learn Lojban: "Homonyms: Their Grate!"
Proud Supporter of the Singularity Institute - http://singinst.org/


  reply	other threads:[~2007-08-26  1:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20070825004026.12883.52907.reportbug@chain.digitalkingdom.org>
2007-08-25 14:51 ` Clint Adams
2007-08-25 17:50   ` Peter Stephenson
2007-08-25 17:54     ` Robin Lee Powell [this message]
2007-08-27  0:11       ` Clint Adams
2007-08-27  2:29         ` Robin Lee Powell
2007-08-25 17:53   ` Robin Lee Powell
     [not found] <20070526205426.GA19686@alea.gnuu.de>
2007-05-27  2:50 ` Bug#426161: zsh: crashes in reverse_menu Clint Adams
2007-05-28 12:29   ` Peter Stephenson
     [not found] <schizo@debian.org>
2007-04-14 20:53 ` release whinging Clint Adams
2007-04-15 18:58   ` Peter Stephenson

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=20070825175422.GC4335@digitalkingdom.org \
    --to=rlpowell@digitalkingdom.org \
    --cc=439425-forwarded@bugs.debian.org \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@sunsite.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).