|
From: Julian S. <js...@ac...> - 2005-11-16 15:31:59
|
To follow up: > - should we be creating a bss segment which is executable as well as > r/w-able? In fact it's the data segment, which with the new aspacemgr was being given permissions rw-, whereas natively it's rwx. So that's an (easily fixable) bug. But it shows a nastier problem. We're trying to execute code in a segment marked without x permission (until said bug is fixed, at least). However, the code being run was is in a place which memcheck (correctly) regards as addressible and defined, so it doesn't complain; instead the program just appears to die with a (synthesised) segfault. What ought to happen, but doesn't, is that an error message should be emitted if either the tool or aspacem believes the (code) address in question is invalid. Problem is there's no way (core/tool iface fn) to tell the tool to notify the user of such an event. J |