Re: coredump completing scp

[Vin Shelton <acs@alumni.princeton.edu>]

Peter -

On Fri, Jan 28, 2011 at 4:56 AM, Peter Stephenson
<Peter.Stephenson@csr.com> wrote:
> On Thu, 27 Jan 2011 19:30:31 -0800
> 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.
>
> 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.

legolas% scp --25509-- REDIR: 0x55636b0 (strcat) redirected to
0x4c27140 (strcat)
--25509-- Reading syms from
/home/acs/tst/lib/zsh/4.3.11-dev-1/zsh/computil.so (0x62ed000)
==25509==
==25509== HEAP SUMMARY:
==25509==     in use at exit: 0 bytes in 0 blocks
==25509==   total heap usage: 0 allocs, 0 frees, 0 bytes allocated
==25509==
==25509== All heap blocks were freed -- no leaks are possible
==25509==
==25509== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
--25509--
--25509-- used_suppression:      2 dl-hack3-cond-1
==25509==
==25509== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 2 from 2)
--25509-- Reading syms from /lib64/libnss_compat-2.11.2.so (0x6502000)
--25509-- Reading syms from /lib64/libnsl-2.11.2.so (0x670b000)
--25509-- Reading syms from /lib64/libnss_nis-2.11.2.so (0x6923000)
--25509-- Reading syms from /lib64/libnss_files-2.11.2.so (0x6b2e000)
--25509-- REDIR: 0x555ff60 (free) redirected to 0x4c25ef4 (free)
==25509== Invalid free() / delete / delete[]
==25509==    at 0x4C25F7B: free (in
/usr/lib64/valgrind/vgpreload_memcheck-amd64-linux.so)
==25509==    by 0x671AD49: init (in /lib64/libnsl-2.11.2.so)
==25509==    by 0x671AE79: _nsl_default_nss (in /lib64/libnsl-2.11.2.so)
==25509==    by 0x6928300: _nss_nis_setpwent (in /lib64/libnss_nis-2.11.2.so)
==25509==    by 0x6504557: internal_setpwent (in /lib64/libnss_compat-2.11.2.so)
==25509==    by 0x6505895: _nss_compat_setpwent (in
/lib64/libnss_compat-2.11.2.so)
==25509==    by 0x55C9E1F: __nss_setent (in /lib64/libc-2.11.2.so)
==25509==    by 0x5586CCB: setpwent (in /lib64/libc-2.11.2.so)
==25509==    by 0x43ECB3: fillnameddirtable (hashtable.c:1382)
==25509==    by 0x5EE0130: scanpmuserdirs (parameter.c:1471)
==25509==    by 0x43D339: scanmatchtable (hashtable.c:381)
==25509==    by 0x43D630: scanhashtable (hashtable.c:444)
==25509==  Address 0x42d05e8 is not stack'd, malloc'd or (recently) free'd
==25509==

Regards,
  Vin