On 2018-03-10 3:39 AM, Raphael Hertzog wrote:
Given your work on the compiler, does it really make sense to try to fix
something in cpputest?
The only clean fix I can think of is to modify the tests to use a real
function pointer instead of 0xdeadbeef. I don't think that an architecture
Hi,
On Fri, 09 Mar 2018, John David Anglin wrote:
> Yes. Function pointers on hppa differ from all other architectures.
[...]
> I applied a patch to gcc-8 to fix the "0xdeadbeef" problem. It adds a
> check to ensure that the pointer points to read accessible memory. It
> also checks that the
On 2018-03-09 7:59 PM, Raphael Hertzog wrote:
Thanks for the report, I forwarded it upstream but it seems strange that
hppa is the only architecture with such a problem. Is there something
special about this architecture that could explain this singularity?
Yes. Function pointers on hppa differ
Control: forwarded -1 https://github.com/cpputest/cpputest/issues/1145
Hi,
On Sun, 04 Mar 2018, John David Anglin wrote:
> It looks like __canonicalize_funcptr_for_compare needs to be improved to
> prevent access fault on garbage pointer, but maybe there's something that
> can be done in
Source: cpputest
Version: 3.8-7
Severity: normal
Dear Maintainer,
The build fails running CppUTestTests:
./CppUTestTests
!!..!..!..!..!
..!..!..!..!..!.!!.!..!...
..!..!..!make[2]: *** [Makefile:3402: tdd] Segmentation fault
Full log
5 matches
Mail list logo
