|query: debugging dynamically generated code debray@CS.Arizona.EDU (2003-10-27)|
|Re: query: debugging dynamically generated code email@example.com (2003-10-31)|
|Re: query: debugging dynamically generated code firstname.lastname@example.org (K.C. Shashidhar) (2003-10-31)|
|Re: query: debugging dynamically generated code email@example.com (James Cownie) (2003-11-08)|
|From:||James Cownie <firstname.lastname@example.org>|
|Date:||8 Nov 2003 01:37:39 -0500|
|Organization:||blueyonder (post doesn't reflect views of blueyonder)|
|Posted-Date:||08 Nov 2003 01:37:39 EST|
> debray@CS.Arizona.EDU (Saumya K. Debray) wrote
>How to people go about debugging code that's being
>Given the amount of interest and activity in JIT compilers and dynamic
>code optimization in recent years, I expect there's a fair amount of
>experience with, and literature on, this topic (though citeseer didn't
>turn up anything obvious). I'd be grateful for any pointers.
I believe that Sun's latest versions of dbx handle this for JIT
compiled Java. (Including the "amusement" that the generated machine
code for JIT compiled Java can be garbage collected and later
re-generated if required).
I don't know if they have published anything on _how_ they do this
(though I expect that the runtime probably has some hooks to let
the debugger know what's going on).
James Cownie <email@example.com>
Etnus, LLC. +44 117 9071438
Return to the
Search the comp.compilers archives again.