https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #13 from Philippe Waroquiers ---
(In reply to Julian Seward from comment #6)
> (In reply to Philippe Waroquiers from comment #5)
> > In the particular case of the lib VEX 'fast allocator', there is
> > no instrumentation of this allocator [.
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #12 from Julian Seward ---
(In reply to Ivo Raisr from comment #11)
> 5904a71c b p_CmpNEZ32_Or32.5344
> 5904a720 b p_CmpNEZ32_And32.5340
> 5904a724 b p_zwiden_load64.5765
> 5904a728 b p_CmpwNEZ64_Or64.5612
> 5904a72c B vex_control
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #11 from Ivo Raisr ---
Indeed:
...
5904a71c b p_CmpNEZ32_Or32.5344
5904a720 b p_CmpNEZ32_And32.5340
5904a724 b p_zwiden_load64.5765
5904a728 b p_CmpwNEZ64_Or64.5612
5904a72c B vex_control<===
5904a748 B vex_traceflags
5904a7
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #10 from Julian Seward ---
(In reply to Ivo Raisr from comment #9)
> Hmm, does not strike me as something obvious...
> 5904a754 B vex_failure_exit
> 58179740 b vex_init_done.25661
> 5904a758 B vex_initdone
> 58113d00 T vex_inject_ir
I thin
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #9 from Ivo Raisr ---
Hmm, does not strike me as something obvious...
...
580e1a50 t varstack_show
58003b80 R version
58108f90 T vex_assert_fail
58108f20 T vex_bzero
5904a72c B vex_control <==
5904a74c B vex_debuglevel
5904a754 B v
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #8 from Julian Seward ---
(In reply to Ivo Raisr from comment #7)
> I hope this will shed some light for a mysterious bug I see on x86/Solaris
> (not amd64/Solaris) which manifests in the following debug output printed
> for almost all gdbse
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #7 from Ivo Raisr ---
I concur.
I hope this will shed some light for a mysterious bug I see on x86/Solaris (not
amd64/Solaris) which manifests in the following debug output printed for almost
all gdbserver_tests:
vex iropt: 4 x unrolling (2
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #6 from Julian Seward ---
(In reply to Philippe Waroquiers from comment #5)
> In the particular case of the lib VEX 'fast allocator', there is
> no instrumentation of this allocator [..]
Ah. Good point. Hmm. Given that VEX is a big(ish)
https://bugs.kde.org/show_bug.cgi?id=381162
--- Comment #5 from Philippe Waroquiers ---
(In reply to Julian Seward from comment #2)
> But that might explain why it works. And why Philippe's self-hosting
> Memcheck runs never detected it: because LibVEX_Alloc_inline will surely
> have rounded t
https://bugs.kde.org/show_bug.cgi?id=381162
Ivo Raisr changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://bugs.kde.org/show_bug.cgi?id=381162
Ivo Raisr changed:
What|Removed |Added
Summary|array overrun in VEX|possible array overrun in
|regist
11 matches
Mail list logo
