Implement grokdump annotations for well-known objects.

Implement grokdump annotations for well-known objects.

R=ulan@chromium.org
TEST=tools/grokdump.py

Committed: https://code.google.com/p/v8/source/detail?r=11684

[Erik Corry, 2012-05-30 13:06:12]

https://chromiumcodereview.appspot.com/10441088/diff/1/tools/grokdump.py
File tools/grokdump.py (right):

https://chromiumcodereview.appspot.com/10441088/diff/1/tools/grokdump.py#newc...
tools/grokdump.py:465: print >>sys.stderr, "WARNING: This is NOT a full
minidump!"
I prefer it if my tools don't SHOUT at me.

[Michael Starzinger, 2012-05-30 13:14:06]

Addressed comments.

https://chromiumcodereview.appspot.com/10441088/diff/1/tools/grokdump.py
File tools/grokdump.py (right):

https://chromiumcodereview.appspot.com/10441088/diff/1/tools/grokdump.py#newc...
tools/grokdump.py:465: print >>sys.stderr, "WARNING: This is NOT a full
minidump!"
On 2012/05/30 13:06:12, Erik Corry wrote:
> I prefer it if my tools don't SHOUT at me.

Done.

[ulan, 2012-05-31 07:54:51]

Cool stuff, LGTM.

[Vitaly Repeshko, 2012-05-31 17:34:19]

Nice to see this evolving. Drive-by comment.

https://chromiumcodereview.appspot.com/10441088/diff/4001/tools/grokdump.py
File tools/grokdump.py (right):

https://chromiumcodereview.appspot.com/10441088/diff/4001/tools/grokdump.py#n...
tools/grokdump.py:741: # #define ROOT_LIST_CASE(type, name, camel_name) \
Updating this stuff is going to be even more painful now. Consider creating a
separate V8 build target to print this info.

[Michael Starzinger, 2012-06-01 09:13:05]

I would love to get to a point were I don't need to use WinDbg anymore.

https://chromiumcodereview.appspot.com/10441088/diff/4001/tools/grokdump.py
File tools/grokdump.py (right):

https://chromiumcodereview.appspot.com/10441088/diff/4001/tools/grokdump.py#n...
tools/grokdump.py:741: # #define ROOT_LIST_CASE(type, name, camel_name) \
On 2012/05/31 17:34:20, Vitaly Repeshko wrote:
> Updating this stuff is going to be even more painful now. Consider creating a
> separate V8 build target to print this info.

Yes, I totally agree. At some point the build system should dump the necessary
information in a separate .py file, that we then can include into grokdump.