SA.NEXT - SA feedback needed

[Mikael Gerdin]

On Friday 31 January 2014 18.19.47 Dmitry Samersoff wrote:
> Hi Everyone,
> 
> I would like to start a discussion about future of hotspot debugger,
> known as serviceability agent or SA.
> 
> How you typically use it? What do you expect from it?  What is missed?

I use it to inspect core files from crashes that are hard to reproduce.
A few bits of functionality I use are:

* the inspector
** primarily for java objects but sometimes for C++ objects as well.
* class browser, both to look at bytecode disassembly and dissasembly of 
compiled code. The disassembler displays oopmap data which is useful for 
debugging GC/compiler interaction bugs.
* jstack stack walking
* the (slightly broken) thread stack visualizer


> 
> Please, share your stories and wishes.
> 
> And please, fill the small quiz:
> 
> 1. How often do you use SA?

Weekly.

> 
> 2. On what platform do you use SA?

Linux, Windows, Solaris

> 
> 3. Do you use it to analyze life processes or coredumps?

Primarily for core files, for live processes it's usually easy enough to call 
functions in the debug vm to print out objects and such.
It's when bugs are hard to reproduce that the SA shines.

> 
> 5. What other debuggers do you use to debug hotspot issues

gdb, dbx, windbg - depending on platform.

/Mikael

> 
> -Dmitry