Displaying 4 results from an estimated 4 matches for "hashtable_find".
Did you mean:
hash_table_find
2008 Apr 26
1
Bug#477931: rsync: Segfaults syncing the linux kernel archive.
...g to sync the linux
> kernel archive using version 3.0.2. It doesn't segfault using
> 2.6.9-2etch2. This has worked for weeks but started happening yesterday.
>
> This is what I got from gdb:
> Program received signal SIGSEGV, Segmentation fault.
> #0 0x0000000000434b84 in hashtable_find (tbl=0x0, key=-1,
> allocate_if_missing=0) at hashtable.c:59
> 59 int key64 = tbl->key64;
> (gdb) bt
> #0 0x0000000000434b84 in hashtable_find (tbl=0x0, key=-1,
> allocate_if_missing=0) at hashtable.c:59
> #1 0x0000000000430278 in check_prior (file=0x2ae3...
2020 Jul 24
1
[Bug 1445] New: conntrackd: segfaults when not disabling internal cache
...al.
==11028== Using Valgrind-3.16.1 and LibVEX; rerun with -h for copyright info
==11028== Command: /usr/sbin/conntrackd -C /etc/conntrackd/conntrackd.conf
==11028==
[Fri Jul 24 12:46:15 2020] (pid=11028) [notice] disabling external cache
==11028== Invalid read of size 8
==11028== at 0x1135B8: hashtable_find (hash.c:72)
==11028== by 0x1184E8: cache_update_force (cache.c:279)
==11028== by 0x11A547: dump_handler (ctnl.c:266)
==11028== by 0x11A547: dump_handler (ctnl.c:257)
==11028== by 0x4870BDB: __callback (in
/usr/lib/x86_64-linux-gnu/libnetfilter_conntrack.so.3.7.0)
==11028== by 0x4AA00...
2008 Mar 26
1
rsync 3.0.1pre -H fails assertion
Wayne,
I have this bug in redhat bugzilla:
https://bugzilla.redhat.com/show_bug.cgi?id=439074
Summary: rsync 3.0.1pre -H fails assertion
Is it ok to pass this kind of bug directly upstream filing a new bug in
bugzilla and linking the fedora bug ?
(There is also a reproducer there)
Simo.
--
Simo Sorce * Red Hat, Inc * New York
2008 Feb 02
2
hardlinks not working with inode number > 2^31
I've been using 3.0.0pre8 to move a Debian archive from one filesystem
to another. This archive contains a daily snapshot of the Debian ftp
site, with common files hardlinked to save space.
I noticed that it was using far more space than necessary. Upon
investigation it seems that all the source files that have inode numbers
greater than 2^31 aren't being hardlinked together at the