Hi,
Boris Zbarsky <[EMAIL PROTECTED]> writes:
> profile-signal-handler is not getting called. I do see a SIGPROF
> delivered to the gnucash-bin process (using 'handle SIGPROF stop' in
> gdb after attaching to the gnucash-bin process), but only once during
> the entire report generation. I also
Ludovic Courtès wrote:
GDB supposedly shows all SIGPROFs that are raised, so if it shows only
one, then something's wrong.
Sure. The wrong thing is that profile-signal-handler is not called, so
never resets the timer, so no more SIGPROFs. Unless I'm misreading the
code.
Can you check the
Hello,
Boris Zbarsky <[EMAIL PROTECTED]> writes:
> Sure. The wrong thing is that profile-signal-handler is not called,
> so never resets the timer, so no more SIGPROFs. Unless I'm misreading
> the code.
Oh, right.
> I can't check the values in the structs it's passed, unfortunately (no
> symb
Ludovic Courtès wrote:
I can't check the values in the structs it's passed, unfortunately (no
symbols here for guile or the libc).
Maybe with `strace(1)' or similar?
Unfortunately, that just shows the pointer to the struct, not the value
in the struct itself
Another (remote) possibili
