|
From: Christoph B. <bar...@or...> - 2006-09-11 08:25:31
|
Am Montag, 11. September 2006 00:41 schrieb Josef Weidendorfer:
> Hi Christoph,
>
> I just checked in a bug fix for this problem. Can you check if
> that fixes this issue for you?
>
> I did not look yet at the other bug (x86_64-specific?).
> I think the biggest problem is that toogling the instrumentation mode
> is not really fully tested.
>
> Josef
Hi,
the bug is still there. The current traceback is:
=3D=3D10690=3D=3D at 0x38014809: fprint_bbcc (global.h:691)
=3D=3D10690=3D=3D by 0x3801593D: print_bbccs_of_thread (dump.c:1550)
=3D=3D10690=3D=3D by 0x38015C3A: vgCallgrind_dump_profile (dump.c:1579)
=3D=3D10690=3D=3D by 0x38007651: vgCallgrind_check_command (command.c:45=
5)
=3D=3D10690=3D=3D by 0x38016CB2: vgCallgrind_run_thread (threads.c:191)
=3D=3D10690=3D=3D by 0x38035FFF: vgPlain_set_running (scheduler.c:218)
=3D=3D10690=3D=3D by 0x38048280: vgPlain_client_syscall (syswrap-main.c:=
812)
=3D=3D10690=3D=3D by 0x38036B7F: vgPlain_scheduler (scheduler.c:721)
=3D=3D10690=3D=3D by 0x38051339: run_a_thread_NORETURN (syswrap-linux.c:=
87)
I've attached a debugger and see the following values in line 691:
bb =3D 0x40210a748
*bb =3D {obj =3D 0x402100a70, offset =3D 591896, next =3D 0x0,=20
sect_kind =3D Vg_SectText, instr_count =3D 0, fn =3D 0x40210a678,=20
line =3D 0, is_entry =3D 0 '\0', bbcc_list =3D 0x40210a7d0,=20
last_bbcc =3D 0x40210a7d0, cjmp_count =3D 0, jmp =3D 0x40210a7a8,=20
jmpkind =3D 0, cjmp_inverted =3D 0 '\0', instr_len =3D 0,
cost_count =3D 0, instr =3D 0x40210a7a8}
b->instr[bb->instr_count-1] seems to be invalid because bb->instr_count is=
0=20
and bb->instr_count-1 is out of range.
Gru=DF
Christoph
|