> After someone's tip, I found a solution to this. Passing the linker > '-z execstack' made it run, no problem. It's funny that Linux didn't > complain about it, but rather just seg-faulted. But the segfault is the complaint. What else would you hope for? In general neither the compiler nor the linker has enough information to reliably warn you of the issue before runtime. It may also be worth noting that making stack memory non-executable by default is a relatively recent change to Linux, done to ameliorate the effectiveness of stack-based code exploits. b -- To unsubscribe from this list: send the line "unsubscribe linux-assembly" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
- References:
- Troubles with JIT compiler
- From: Scott Sibley
- Re: Troubles with JIT compiler
- From: Robert Plantz
- Re: Troubles with JIT compiler
- From: Scott Sibley
- Re: Troubles with JIT compiler
- From: Robert Plantz
- Re: Troubles with JIT compiler
- From: Scott Sibley
- Re: Troubles with JIT compiler
- From: Scott Sibley
- Troubles with JIT compiler
- Prev by Date: Re: Troubles with JIT compiler
- Next by Date: how to get the system hardware information
- Previous by thread: Re: Troubles with JIT compiler
- Next by thread: how to get the system hardware information
- Index(es):