Handling Segfaults

What is the most portable way to catch segfaults together with their addresses and then resuming at the place where it happened? I.e. to handle array out of bounds exception by expanding array.

I know it is done with signal() on POSIX and with SetUnhandledExceptionFilter() on Windows. But you cant define signal() for Windows, because it has its own stripped down version, useful only for the purpose of handling CTRL-C.

Both don't signal() and SetUnhandledExceptionFilter() have no means of recovering from error.

>>40
Kernel32/User32/Crss/Gdi32 is just a layer over
https://en.wikipedia.org/wiki/Native_API

>>38
Exceptions-related boilerplate slow down startup time and pollute CPU caches.

>>42
Only GCC hacks to emulate SEH, SEH is zero-cost itself.
https://stackoverflow.com/questions/15670169/what-is-difference-between-sjlj-vs-dwarf-vs-seh

>>41

In other words you have Python, which has bindings to C++/Boost, which wraps over libc, which wraps over kernel32, which wraps over ntdll, which wraps over ntoskrnl.exe, which wraps over device drivers, which wrap over some virtualization framework or Wine running on some OSX or Linux or even Windows. And so ad infinitum.

>>44
Not only that consider the complexity of CPUs executing microcode programs and firmware
https://github.com/jbangert/trapcc

>>42
Have you numbers to show me the difference? I suspect the difference is about 1000 cpu cycles in unneeded overhead and 1000 instances of cache misses for each time you run the program.

>>46

depends on how you use the executable. If you use it in a tight bash loop, then it counts or it is huge highly used executable, like Firefox, half of which consists of boilerplate.

>>40
Great job turbonerd, everyone now knows what a whizkid you are with your little shitsembler. Wow, no one cares! We were clearly talking about C, and the only thing you have shown is that you have nothing to offer anyone and you're going to die alone. Get a life, loser.

>>48
Rude.

>>41

RtlAdjustPrivilege

lol

>>49
I'm rude? >>40 chan just whipped out his cock and started beating off to his own self-image right in front of us. He's the rude obe!

>>48
you know it's disassembled C code, right? IHBT?

>>9
So you just run everything in debug mode. G-d, sometimes I think everyone but me is retarded.

>>53
Debug mode adds bloat.

>>52
No it isn't, stop slandering me. What makes you think that it's disassembly? What compiler would produce anything like that without startup\breakdown code, and not linking to kernel32 (you know, the entire point)? What disassembler even outputs FASM syntax? Just because you can't do something, don't assume no one can, /g/-kun.

>>41,48
Turds!

Ended up with following code: https://github.com/saniv/symta/blob/master/runtime/w/ctx.c

More like smegfaults, amirite