zsh-workers
 help / color / mirror / code / Atom feed
From: Nicolas George <nicolas.george@ens.fr>
To: Peter Stephenson <pws@csr.com>
Cc: zsh-workers@sunsite.dk, 249627@bugs.debian.org
Subject: Re: Bug#249627: Alias + LC_CTYPE + function => segmentation fault
Date: Wed, 19 May 2004 19:36:58 +0200	[thread overview]
Message-ID: <20040519173658.GA26842@clipper.ens.fr> (raw)
In-Reply-To: <3684.1084960653@csr.com>

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

Le primidi 1er prairial, an CCXII, Peter Stephenson a écrit :
> I don't think this is the same problem, since the programme finishes
> correctly.  It does indicate something funny in saving and restoring
> environment variables.

If it is a memory corruption caused by an invalid free, it is likely
that valgrind would either prevent it, or change the exact place where
the corruption occurs, thus changing the time it results in a
segmentation fault. I have seen that just having used "setopt" earlyer
changed a segfault on the second try into an infinite loop in the third
try: this problem is very sensitive to initial conditions.

I have tried Electric Fence, here is a backtrace, just after the second
date:

ssecem% date

ElectricFence Aborting: free(403cdfe8): address not from malloc().

Program received signal SIGILL, Illegal instruction.
[Switching to Thread 1075767072 (LWP 1967)]
0xffffe410 in __kernel_vsyscall ()
(gdb) where
#0  0xffffe410 in __kernel_vsyscall ()
#1  0x400ce156 in kill () from /lib/tls/i686/cmov/libc.so.6
#2  0x4002719b in EF_Abort () from /usr/lib/libefence.so
#3  0x40026ac1 in free () from /usr/lib/libefence.so
#4  0x0808dc1e in zsfree (p=0x403cdfe8 "") at mem.c:1399
#5  0x0809b2d2 in delenv (x=0x403cdfe8 "") at params.c:3455
#6  0x080698f4 in save_params (state=0xbffff7c0, pc=0x406d915c, 
    restore_p=0xbffff568, remove_p=0xbffff56c) at exec.c:2523
#7  0x08069314 in execcmd (state=0xbffff7c0, input=0, output=0, how=18, 
    last1=2) at exec.c:2371
#8  0x08065e47 in execpline2 (state=0xbffff7c0, pcode=387, how=18, input=0, 
    output=0, last1=0) at exec.c:1276
#9  0x08065381 in execpline (state=0xbffff7c0, slcode=6146, how=18, last1=0)
    at exec.c:1066
#10 0x08064cce in execlist (state=0xbffff7c0, dont_change_job=0, exiting=0)
    at exec.c:872
#11 0x080649ee in execode (p=0x406d9128, dont_change_job=0, exiting=0)
    at exec.c:773
#12 0x0807b253 in loop (toplevel=1, justonce=0) at init.c:165
#13 0x0807d99f in zsh_main (argc=1, argv=0xbffff8f4) at init.c:1274
#14 0x080521e6 in main (argc=1, argv=0xbffff8f4) at main.c:37

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

      reply	other threads:[~2004-05-19 17:38 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
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 [this message]

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=20040519173658.GA26842@clipper.ens.fr \
    --to=nicolas.george@ens.fr \
    --cc=249627@bugs.debian.org \
    --cc=pws@csr.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).