188248 - Add string decoding to codesigh's symbol demangling

Status: RESOLVED FIXED

(Core :: XPCOM, defect)

Description

[Alec Flett]

Playing with codesighs (well, msmap2tsv, specifically) I was running into lots
of symbols that would demangle to "`string'"

This was kind of frustrating because I had no idea what string it referred to.
I played around a bit and was able to reverse-engineer the string-to-symbol
mapping and integrate the decoding into msmap2tsv - so that instead of getting
`string' we get "string: " followed by the actual string value. Since these are
actually symbols, and no the strings themselves, the symbol is just a mangled
version of the first 20 or so characters of the string, so sometimes you get
stuff like
"You can't dereference a NULL nsC"

so I added elipses to such strings, so the resulting demangled symbol name is:
string: "You can't dereference a NULL nsC..."

which should make it easy to grep for, and so forth.

patch forthcoming.

Comment 1

[Alec Flett]

Attachment: decode strings

and here's the decoding algorithm. The mechanism is described in the bug.

Comment 2

[Alec Flett]

Comment on attachment 110988 [details] [diff] [review]
decode strings

Garrett - do you mind reviewing? this would be really helpful for codesighs

Comment 3

[Garrett Arch Blythe]

Comment on attachment 110988 [details] [diff] [review]
decode strings

Looks good to me, Alec.

Comment 4

[Alec Flett]

thanks - I figured out a bit more about the string decoding as well (such as the
strings that were previously turning into empty strings) so I checked that in as
well - it was just 2-3 more states to the lexer that is in this patch.