By it's nature a core dump would be operating system specific. Since that is not the intent of Java you will have a hard time doing this. Perhaps a native method that calls system specific C code would work.
"JavaRanch, where the deer and the Certified play" - David O'Meara
Thanks Cindy for the response. Means, one of the way to debug is, attach Java interpreter session to "jdb" while running the application . Correct ? Sudhir
Well, some of the IDE's have nice debugging features (one of the major reasons some people use them), but I am not sure what you mean by attaching a Java interpreter session.
"JavaRanch, where the deer and the Certified play" - David O'Meara
Thanks for the response Cindy. Means , the only way to find problem at run time for application crashing is to attach "jdb" to Java interpreter session . Correct ? For that you have to simulate or wait for occurence of the problem. Sudhir
Oops !! my question got repeated (i was not able to see my reply so typed again) Attaching a JVM , i mean, attaching to active JVM on which application is running. Nothing but debugging with "jdb". Do you know any IDE or anything which gives information of what happened at the time of crashing ? Thanks.