Gopal V wrote:
If memory serves me right, Leopold Toetsch wrote:Yep, you are right - I did miss this point sometimes. We have to do a _save_registers before calling code, that might throw an exception.
Excuse me for butting in ... But how are the parameters to a C code being passed .. I assume that would use a stack or register
stack
I guess pushall,call,popall would be the easiest approach
pusha/popa is overkill. The called functions always save bp and bx,di,si when used. ax is the return value, remaining is dx (cx is used by shifts) - i386 of course.
Speaking about debugging calls from JIT'd code ... Does parrot JIT generate a debugging segment ? like a dwarf2 segment so that we can
debug with gdb ? ... (I hate it when I see 200 ?? in a backtrace).
That would be a really nice feature. Can we - and how - handle over debug info to a running gdb?
I'm a man of simple ideas ... :-) Gopal
leo
