On 10/12/07, Alexei Fedotov <[EMAIL PROTECTED]> wrote: > > +1 > NCAI adds very useful architectural level for VM internal debugging > and defensive programming. The best example is a crash handler, but > other utilities such us self-detection of deadlocks, is also quite > interesting.
NCAI could be interface to build some kind of viewer, but no real debugger. 1. It couldn't be very useful just because it's single process debugging model and if you set breakpoint incorrectly you could lock whole JVM. 2. building debugger from the very beginning you try to invent wheel once again, you have to develop new mechanisms that already exists in native debuggers. 3. building infrastructure for Mixed Mode debugging using native debugger could be implemented in 1-2 month and it'll be really powerful and useful solution especially JNI developers. HP(gdb) and Sun (dbx) already introduced native debugger-centric solutions for debugging in mixed environments. So NCAI seams to be potential dead code and I won't be surprised if year or two later you'll be voting for removing this code. On 10/12/07, Vasily Levchenko <[EMAIL PROTECTED]> wrote: > > Hi Mikhail, > > Have you got any idea how to use it? Except "Integrated Debugger for > > Java/JNI environment" (former MMD). > > > > On 10/12/07, Mikhail Loenko <[EMAIL PROTECTED]> wrote: > > > > > > We now have all requisite paperwork in place for > > > http://issues.apache.org/jira/browse/HARMONY-4689, so let's vote to > > > accept: > > > > > > [ ] +1 Accept this contribution > > > [ ] -1 Reject because... > > > > > > As usual, 3 days unless someone complains they need more time. > > > > > > > > > > > -- > > --vvl > > > > > -- > With best regards, > Alexei, > ESSD, Intel > -- --vvl
