From: Peter Stephenson <pws@csr.com>
To: "Christoph Bauer" <Christoph.Bauer@lmsintl.com>
Cc: zsh-workers@sunsite.dk
Subject: Re: zsh 4.3.4 released
Date: Mon, 23 Apr 2007 15:01:07 +0100 [thread overview]
Message-ID: <200704231401.l3NE177w006880@news01.csr.com> (raw)
In-Reply-To: <BB046CA812535C45BD0029AA9D04BA79C66F39@KL-SRV57.lmsintl.com>
(Moved to zsh-workers.)
"Christoph Bauer" wrote:
> Two short remarks:
> - HP-UX 11: I need to define _INCLUDE__STDC_A1_SOURCE to compile zsh
> with HP's cc.
> (set CFLAGS=3D"$OTHER_CFLAGS -D_INCLUDE__STDC_A1_SOURCE")
Thanks for the report. Is there anyway we can tell that this needs
defining?
> - on SGI zsh-4.3.4 crashes immediatly:
> Starting program: /projekte/backup/tools/unix/sgi6n3/bin/zsh-4.3.4=20
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x1005b328 in optlookup ()
> (gdb) where
> #0 0x1005b328 in optlookup ()
> #1 0x1005b0c4 in bin_setopt ()
> #2 0x1000e8f8 in execbuiltin ()
> #3 0x1000e8f8 in execbuiltin ()
> Previous frame identical to this frame (corrupt stack?)
I don't have an SGI around and there isn't any suspicious-looking code
in optlookup() (though it has recently changed). Are you able to
compile with --enable-zsh-debug and see what "name" is being passed to
the last frame ("show name")? Alternatively, can you see which "setopt"
statement is causing the problem, or does it happen with a lot of
different varieties of statement?
--
Peter Stephenson <pws@csr.com> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
To access the latest news from CSR copy this link into a web browser: http://www.csr.com/email_sig.php
To get further information regarding CSR, please visit our Investor Relations page at http://ir.csr.com/csr/about/overview
next prev parent reply other threads:[~2007-04-23 14:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200704161647.l3GGl2FE027950@news01.csr.com>
[not found] ` <20070419120758.e9774528.pws@csr.com>
2007-04-19 19:44 ` Paul Ackersviller
[not found] ` <237967ef0704201440g1c072ca8l451439d2ec8578bf@mail.gmail.com>
[not found] ` <20070423104151.1f5f368e.pws@csr.com>
[not found] ` <237967ef0704230550k41ddb13fy60deebd526ecc5ec@mail.gmail.com>
2007-04-23 13:18 ` Peter Stephenson
2007-04-23 14:22 ` Mikael Magnusson
2007-04-23 15:06 ` Peter Stephenson
2007-04-23 16:00 ` Mikael Magnusson
2007-04-23 16:40 ` Peter Stephenson
2007-04-23 17:07 ` Peter Stephenson
2007-04-23 17:18 ` Mikael Magnusson
2007-04-23 16:07 ` Mikael Magnusson
[not found] ` <BB046CA812535C45BD0029AA9D04BA79C66F39@KL-SRV57.lmsintl.com>
2007-04-23 14:01 ` Peter Stephenson [this message]
[not found] ` <BB046CA812535C45BD0029AA9D04BA79C66F72@KL-SRV57.lmsintl.com>
2007-04-23 15:14 ` 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=200704231401.l3NE177w006880@news01.csr.com \
--to=pws@csr.com \
--cc=Christoph.Bauer@lmsintl.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).