zsh-workers
 help / color / mirror / code / Atom feed
From: Frank Terbeck <ft@bewatermyfriend.org>
To: Philipp Hartwig <ph.hartwig@googlemail.com>
Cc: zsh-workers@zsh.org
Subject: Re: segfault on menu-select
Date: Thu, 12 Aug 2010 19:07:38 +0200	[thread overview]
Message-ID: <87r5i34v51.fsf@ft.bewatermyfriend.org> (raw)
In-Reply-To: <20100812165307.GA24998@ph> (Philipp Hartwig's message of "Thu, 12 Aug 2010 18:53:07 +0200")

Philipp Hartwig wrote:
>> Still. Can you reproduce this with CVS HEAD?
>
> Building this was not so easy. Installing the man pages (and hence a
> normal make install) still fails, but make, make check, make
> install.bin, make install.modules were successful and yes, I can
> reproduce the issue. Still not with zsh -f of course, but with the
> minimal .zshrc from before.

To generate the manuals, you need the `yodl' package.

>> If it's reproducible with CVS HEAD, it would be good to create a debug
>> build and fetch a back trace from the core file.
>
> Sorry, I don't know what that means but I'll be happy to follow any
> instructions.

>From a fresh checkout, here's what I usually do:

% ./Util/preconfig
% /configure  --enable-cap --enable-function-subdirs \
              --enable-largefile --enable-maildir-support \
              --enable-multibyte --enable-pcre --enable-zsh-debug
% make
% su
# make install

Then when you've crashed the application, you can load the core file
together with the program's binary and use the "bt full" command to
produce a backtrace.

To put the backtrace to a file, the following oneliner works:

% gdb -c core /usr/local/bin/zsh <<< $'bt full\nquit\n' > backtrace.txt

Where `core' is the core file and `/usr/local/bin/zsh' being the
installed zsh binary which you just crashed.

The backtrace will only be useful if the zsh binary is from a debugging
build.

Regards, Frank


  reply	other threads:[~2010-08-12 17:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-12 14:46 Philipp Hartwig
2010-08-12 14:53 ` Frank Terbeck
2010-08-12 15:20   ` Philipp Hartwig
2010-08-12 15:49     ` Frank Terbeck
2010-08-12 16:53       ` Philipp Hartwig
2010-08-12 17:07         ` Frank Terbeck [this message]
2010-08-12 17:33           ` Philipp Hartwig
2010-08-12 18:04             ` Frank Terbeck
2010-08-12 23:07             ` Bart Schaefer
2010-08-13  8:08               ` Philipp Hartwig
2010-08-13 15:57                 ` Bart Schaefer
2010-08-13 20:43                   ` Peter Stephenson
2010-08-15 20:43                     ` Bart Schaefer
2010-08-15 22:34                       ` Bart Schaefer
2010-08-31 14:33                         ` Philipp Hartwig
2010-09-06  4:11                           ` Bart Schaefer
2011-01-09 18:56                             ` Philipp Hartwig
2011-01-09 19:54                               ` Bart Schaefer
2011-01-09 20:57                                 ` Philipp Hartwig
2010-08-12 16:04   ` Bart Schaefer
2010-08-12 17:03     ` Philipp Hartwig

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=87r5i34v51.fsf@ft.bewatermyfriend.org \
    --to=ft@bewatermyfriend.org \
    --cc=ph.hartwig@googlemail.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).