zsh-workers
 help / color / mirror / code / Atom feed
From: Vin Shelton <acs@alumni.princeton.edu>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-workers@zsh.org
Subject: Re: coredump completing scp
Date: Thu, 27 Jan 2011 22:46:14 -0500	[thread overview]
Message-ID: <AANLkTinPnewv-kUpeNvT97xo0tG-VwGMnWnjDvgeQaS7@mail.gmail.com> (raw)
In-Reply-To: <110127193031.ZM4926@torch.brasslantern.com>

On Thu, Jan 27, 2011 at 10:30 PM, Bart Schaefer
<schaefer@brasslantern.com> wrote:
> On Jan 27, 10:13pm, Vin Shelton wrote:
> }
> } This shell was configured --with-zsh-mem and that seems to be required
> } to provoke the coredump.
> }
> } #11 0x00007fd2d8b57ccc in setpwent () from /lib64/libc.so.6
> } #12 0x000000000043ecb4 in fillnameddirtable (ht=0x6e4b08) at hashtable.c:1382
> }
> } Please let me know if any further info is needed.
>
> Operating system and compiler?
>
> This looks like an incompatibility of the libc free() which is
> being invoked from within setpwent() and the zsh-supplied memory
> routines.  There's probably not a lot to be done about it except to
> avoid using --with-zsh-mem on your platform.
>

opensuse 11.3:

Linux legolas 2.6.34.7-0.7-desktop #1 SMP PREEMPT 2010-12-13 11:13:53
+0100 x86_64 x86_64 x86_64 GNU/Linux

gcc (SUSE Linux) 4.5.0 20100604 [gcc-4_5-branch revision 160292]


  - Vin


  reply	other threads:[~2011-01-28  3:46 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-28  3:13 Vin Shelton
2011-01-28  3:30 ` Bart Schaefer
2011-01-28  3:46   ` Vin Shelton [this message]
2011-01-28  9:56   ` Peter Stephenson
2011-01-28 10:14     ` Peter Stephenson
2011-01-29  1:42     ` Vin Shelton
2011-01-29 22:16       ` Peter Stephenson
2011-01-29 23:13         ` Bart Schaefer
2011-01-29 23:33           ` Peter Stephenson
2011-01-30  5:51             ` Bart Schaefer
2011-02-15 19:02               ` 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=AANLkTinPnewv-kUpeNvT97xo0tG-VwGMnWnjDvgeQaS7@mail.gmail.com \
    --to=acs@alumni.princeton.edu \
    --cc=schaefer@brasslantern.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).