https://bugs.kde.org/show_bug.cgi?id=356457
--- Comment #13 from Philippe Waroquiers <philippe.waroqui...@skynet.be> ---
(In reply to Joost VandeVondele from comment #12)
Thanks for this data.
The warning about the stack switch is normal : valgrind has an heuristic to
detect stack switch. If a program uses huge stackframes, then a call can be
confused
with a stack switch, and this warning indicates what to do if this is *not* a
stack switch
(but in a self-hosting setup, such message is normal: it is a stack switch, not
a huge frame).
Sadly, no error is detected by the self-hosting.
So, there are a few more things you could try:
Run (no need to self host, just a normal run) but add the option
--sanity-level=4
Valgrind will do (more) sanity checks while running, and maybe this might give
a hint.
Another thing is to add the option --vgdb-stop-at=valgrindabexit
when you run all your regression tests. And then, when the problem reproduces,
valgrind will stop and wait for a gdb to connect.
Then attach with gdb to the valgrind process and do e.g.
bt full
Also to the frame (image.c:778) and do
print img->ces[i]->off
print img->ces[i]->used
You might also print all the not null ces entries.
But we are really trying to kill the bug by shooting in the dark :(
> Since the error is recurring, I have now tried to run the self-hosting.
> Running :
>
> /data/vjoost/test/outer/install/bin/valgrind --sim-hints=enable-outer
> --trace-children=yes --smc-check=all-non-file --run-libc-freeres=no
> --tool=memcheck -v /data/vjoost/test/inner/install/bin/valgrind
> --suppressions=/data/vjoost/toolchain-r16494/install/valgrind.supp
> --max-stackframe=2168152 --error-exitcode=42 --vgdb-prefix=./inner
> --core-redzone-size=1000 --tool=memcheck -v
> /data/schuetto/auto_regtesting/regtests/cp2k/exe/local_valgrind/cp2k.sdbg
> ethanol_both_rcut10.0_e1-1_v1-4_RSR.inp
>
> (I.e. self-hosting with added redzone, on the our executable corresponding
> to a failed run, with its arguments and parameters), I get a seemingly
> correct run. The output will be attached as out.innerouter.2 . Maybe it is
> worthwhile to look with expert eyes.
>
> However, after observing in that output a warning on stack switching, I
> added --max-stackframe=68009224472 (as suggested, seems a bit large;-), and
> that lead to a run with some other error (Memcheck: the 'impossible'
> happened: create_MC_Chunk: shadow area is accessible).
--
You are receiving this mail because:
You are watching all bug changes.
