Re: [Chicken-hackers] How to interpret chicken post mortem?

[Jörg F . Wittenberger]

Am 26.11.2015 um 13:56 schrieb Jörg F. Wittenberger:
> Am 26.11.2015 um 11:34 schrieb Peter Bex:
>> On Thu, Nov 26, 2015 at 11:29:20AM +0100, Jörg F. Wittenberger wrote:
>>> Something is definitely wrong at master and it is non-deterministic.
...
>>> (if (let ((g10816 key)) (trstcntl#x509-subject-hash cert))
>>>   (let ((t10269 ...)) (let (...) (util#remove-file ...)))
>>>   (##core#undefined))
>>>
>>> Error: (assq) bad argument type: #<invalid immediate object>
>>
>> Do you also get this when compiling said code with the 4.10.1 snapshot?
> 
> So far i did not try.
...

> I'll report when it breaks.

Sure still on master.  This time the gdb stack trace may be enlightening.

(Let me promise one thing: this wt-tree code is innocent. I was not
touched for many years and is heavily used.)

So obviously t4...t7 are loaded from rather strange addresses here:

#0  f_4526 (c=7, av=0xbe186050) at wttree.c:4637
4637    C_word ab[13],*a=ab;
[Current thread is 1 (Thread 0x4009a210 (LWP 7600))]
(gdb) bt
#0  f_4526 (c=7, av=0xbe186050) at wttree.c:4637
#1  0x00146b54 in f_3409 (c=<optimized out>, av=<optimized out>)
    at wttree.c:6087
#2  0x001470a4 in f_4320 (c=<optimized out>, av=0xbe187a14) at wttree.c:1696
#3  0x00145990 in f_7008 (t0=<optimized out>, t1=-1105692140,
    t2=<optimized out>, t3=<optimized out>,
    t4=<error reading variable: Cannot access memory at address 0x6>,
    t5=<error reading variable: Cannot access memory at address 0x6>,
    t6=<error reading variable: Cannot access memory at address 0x6>,
    t7=<error reading variable: Cannot access memory at address 0x9>)
    at wttree.c:7604
#4  0x0014eff0 in f_4511 (c=<optimized out>, av=<optimized out>)
    at wttree.c:4793
#5  0x0014f320 in f_4658 (c=<optimized out>, av=0xbe1862c0) at wttree.c:2947

Does this help in any way?

Best

/Jörg

signature.asc
Description: OpenPGP digital signature