Roman Kennke wrote: > > If gcj cannot reliably walk the stack at the moment, > > I just want to add one comment here. The problem (at least as we found > it @aicas) is not to reliably walk the stack, the problem is that the > VMStackWalker interface is not well suited for 'walking' the > stack. Again, I think you misunderstand the purpose of the VM interface. It does not exist to provide handy or convenient methods to use in your own code, it simply tries to define the absolute minimum that GNU Classpath requires from the VM. If you need more powerful stack walking in your own code, by all means add an API to do this, but only when this code is part of GNU Classpath does it make sense to add it to the VM interface. Regards, Jeroen
