Closed GoogleCodeExporter closed 9 years ago
Thanks for reporting it. I don't test on suse. Have you tried earlier versions
of gperftools? I asking to try to figure out if it's some recent regression or
something older.
Original comment by alkondratenko
on 20 Sep 2014 at 9:29
Hm. Exit code 132 appears to be exit due to signal SIGILL.
Please check some obvious things like if your ram is ok.
Original comment by alkondratenko
on 20 Sep 2014 at 9:47
At least on suse 12.3 amd64 under docker tests pass on my box.
Original comment by alkondratenko
on 20 Sep 2014 at 11:51
Tests pass for me also under KVM. With and without libunwind.
Original comment by alkondratenko
on 21 Sep 2014 at 12:59
Going to assume it's your bad ram (due to SIGILL). Please reopen if you can
still reproduce this cleanly.
Original comment by alkondratenko
on 29 Nov 2014 at 7:17
Original issue reported on code.google.com by
alexande...@googlemail.com
on 20 Sep 2014 at 8:13Attachments: