https://bugs.kde.org/show_bug.cgi?id=369175
--- Comment #6 from Mark Wielaard <m...@redhat.com> --- (In reply to Julian Seward from comment #3) > I tried to reproduce this on gcc112.fsffrance.org (a P8 system) but failed -- > it runs OK. I'd be happy to chase this if I could reproduce on a machine > that I can access. gcc112 is ppc64le which seems to work fine. Unfortunately the ppc64[be] machines in the GCC compile farm are all power7, not power8 (as gcc112 is). > (3) with --tool=none, run it with --trace-flags=10001110 and > --trace-notbelow= set to the appropriate value so you actually > get output for the failing block. From that we might be able > to guess what the problem is. It is sometimes convenient to do that from gdb. Run with ./vg-in-place --vgdb-error=0 none/tests/ppc64/test_isa_2_07_part1 in one terminal gdb none/tests/ppc64/test_isa_2_07_part1 in another. Attach in gdb with target remote | coregrind/vgdb. continue. It gets the SEGV. Find the address where it crashed. Then use monitor v.translate <address> [<traceflags>] to dump the block. The traceflags are the same. See http://www.valgrind.org/docs/manual/manual-core-adv.html#manual-core-adv.valgrind-monitor-commands -- You are receiving this mail because: You are watching all bug changes.
