zsh-workers
 help / color / mirror / code / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: Clint Adams <schizo@debian.org>
Cc: zsh-workers@sunsite.dk, 249627-forwarded@bugs.debian.org
Subject: Re: Bug#249627: Alias + LC_CTYPE + function => segmentation fault
Date: Tue, 18 May 2004 18:39:03 +0200	[thread overview]
Message-ID: <20040518163903.GA29789@clipper.ens.fr> (raw)
In-Reply-To: <20040518155325.GA6069@scowler.net>

[-- Attachment #1: Type: text/plain, Size: 871 bytes --]

Le decadi 30 floréal, an CCXII, Clint Adams a écrit :
> I can't reproduce this myself.  Does gdb tell you anything?

That's strange, I have the same symptoms on several Debian Sarge
installations, but not all situation I test. I have built
zsh_4.2.0.orig.tar.gz without the Debian patches, and the problem is
still there. Here is a backtrace:

Program received signal SIGSEGV, Segmentation fault.
0x4011513c in mallopt () from /lib/tls/i686/cmov/libc.so.6
(gdb) where
#0  0x4011513c in mallopt () from /lib/tls/i686/cmov/libc.so.6
#1  0x00000000 in ?? ()
#2  0x4039c174 in ?? ()
#3  0x00000005 in ?? ()
#4  0xbffff598 in ?? ()
#5  0x08087581 in newparamtable ()
Previous frame inner to this frame (corrupt stack?)

I can send (or rather upload on an anonymous FTP) you a core file, the
binary, or even the whole build tree, if you find it necessary.

[-- Attachment #2: Type: application/pgp-signature, Size: 185 bytes --]

  reply	other threads:[~2004-05-18 16:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040518152257.GA11291@clipper.ens.fr>
2004-05-18 15:53 ` Clint Adams
2004-05-18 16:39   ` Nicolas George [this message]
2004-05-18 18:57     ` Clint Adams
2004-05-18 19:30       ` Nicolas George
2004-05-19  9:57         ` Peter Stephenson
2004-05-19 17:36           ` Nicolas George

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=20040518163903.GA29789@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=249627-forwarded@bugs.debian.org \
    --cc=schizo@debian.org \
    --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).