I wouldn't think it's safe to use the 1.0.4 header file with 1.1.0, considering that it expands to some magic assembler code that valgrind recognizes at runtime. What macros have disappeared in 1.1.0?
/ Martin Stjernholm, Roxen IS
Previous text:
2002-12-11 22:32: Subject: gcc 3.2
I got the same error if I compile --without-copt --without-mmx --without-threads. (mmx needs -O to work.)
Valgrind 1.1.0 halts immediately on:
| Memcheck: mc_main.c:607 (set_address_range_perms): Assertion `vgSkin_cheap_sanity_check()' failed. | | sched status: | | Thread 1: status = Runnable, associated_mx = 0x0, associated_cv = 0x0 | ==22005== at 0x80FD1EE: alloc_more_mapping (in /tmp/pikevalgrind/test-install/pike/7.5.1/bin/pike) | ==22005== by 0x80FD214: alloc_mapping (in /tmp/pikevalgrind/test-install/pike/7.5.1/bin/pike) | ==22005== by 0x80FDAAD: debug_allocate_mapping (in /tmp/pikevalgrind/test-install/pike/7.5.1/bin/pike) | ==22005== by 0x80810B4: init_builtin_constants (in /tmp/pikevalgrind/test-install/pike/7.5.1/bin/pike) | | Please report this bug to: jseward@acm.org
The 1.1.0 header file lacks the macros Pike is using, so I used the 1.0.4 header file. I don't know if that matters.
Does Pike do anything wierd I should know about if I (as instructed) report the bug to valgrind author?
/ Mirar