Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: coredump completing scp
- X-seq: zsh-workers 28669
- From: Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: coredump completing scp
- Date: Sat, 29 Jan 2011 22:16:25 +0000
- In-reply-to: Message from Vin Shelton <acs@alumni.princeton.edu> of "Fri, 28 Jan 2011 20:42:17 EST." <AANLkTikaArDyk7seZO_uy7=E=OyA9uwWkqeC_EO9AYZZ@mail.gmail.com>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Vin Shelton wrote:
> > If you have valgrind, running "valgrind zsh -f" might be useful. (I
> > don't think you'd need any of the options to look for leaked memory
> > for something like this.)
>
> Thanks for the suggestion. Here's the report from valgrind. The call
> to setpwent is made from fillnameddirtable in hahstable.c. I don't
> really know what else to make of this, though.
Me neither, I'm afraid. It certainly *looks* like an error within
setpwent itself, though that doesn't necesarily mean it is. As valgrind
is claiming the memory wasn't malloc'd at all it doesn't give us much of
a lead.
--
Peter Stephenson <p.w.stephenson@xxxxxxxxxxxx>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/
Messages sorted by:
Reverse Date,
Date,
Thread,
Author