The Hermit Hacker wrote:
>
> I am just creating this now...this is to be considered the first *releaes*
> candidate for v6.5 ...
>
> I expect there to be *no more* commits to the source tree until after a
> formal release is done...
Ah. I wanted to implement proper handling of case when tuple in
update-chain is updated by "too old" xaction (part of chain should
be deleted) but ok - it's not bug, just unimplemented feature.
(BTW, Mark, I have to update lock.sgml)
Hiroshi, please run your test. You'll get NOTICEs instead of ERRORs.
Unfortunately, I can't get your test finished locally - I always
get core and gdb says too little:
#0 0x2823452f in strcpy ()
(gdb) bt
#0 0x2823452f in strcpy ()
#1 0xefbf8944 in ?? ()
#2 0x812d19d in hash_search (hashp=0x1c518bfc, keyPtr=0x8901428d <Address 0x8901428d
outof bounds>, action=1233853505, foundPtr=0x4d89410c <Address 0x4d89410c out of bounds>) at dynahash.c:651
#3 0x4d8b0000 in ?? ()
Cannot access memory at address 0x3c7.
(gdb) f 2
#2 0x812cfbd in hash_search (hashp=0x1c518bfc, keyPtr=0x8901428d <Address 0x8901428d
outof bounds>, action=1233853505, foundPtr=0x4d89410c <Address 0x4d89410c out of bounds>) at dynahash.c:651
651 memmove(destAddr, keyPtr, hctl->keysize); ^^^^^^^
??? memmove shouldn't call strcpy. Something is broken,
but maybe due to FreeBSD 3.0 on my box... I'll run test
on 2.2.6 soon.
Vadim