Developer forums (C::B DEVELOPMENT STRICTLY!) > Development

How do i decypher codeblocks.rpt ?

<< < (2/4) > >>

rickg22:

--- Quote from: tiwag on August 05, 2005, 08:16:33 pm ---use the /devel/codeblocks with debug symbols in it to get symbolic information in the rpt

--- End quote ---

And how exactly do i do that? the .rpt file wasn't generated by me but by the bug submitter.

tiwag:

--- Quote from: rickg22 on August 05, 2005, 08:17:34 pm ---
--- Quote from: tiwag on August 05, 2005, 08:16:33 pm ---use the /devel/codeblocks with debug symbols in it to get symbolic information in the rpt

--- End quote ---

And how exactly do i do that? the .rpt file wasn't generated by me but by the bug submitter.

--- End quote ---

that's a dilemma - :shock: - it only works with the debug-version 
the adresses are different with & without debug symbols,
so you can't look easily which adress corresponds to each version.
moreover you would need map files of each dll ... a horror - normally it isn't worth the expense

can't you send the submitter a development debug-version of codeblocks?
or try to reproduce the crash with your debug-version.

David Perfors:
Then I think we have to strip the strip command from the update file and always release debug versions, except when we know the version is bug free :)

rickg22:
Good idea :P

mandrav:

--- Quote from: rickg22 on August 05, 2005, 08:17:34 pm ---
--- Quote from: tiwag on August 05, 2005, 08:16:33 pm ---use the /devel/codeblocks with debug symbols in it to get symbolic information in the rpt

--- End quote ---

And how exactly do i do that? the .rpt file wasn't generated by me but by the bug submitter.

--- End quote ---

There is a nice command line utility called addr2line. Surprise! It can decipher the reported address and map it to source file and line!
How to use it (based on your example rpt):

1) You must be doing this with the exact same C::B build (with that of the user that sent you the .rpt) or the info will be garbage
2) Go to *your* devel folder (where the unstripped .exe and .dll resides)
3) Issue "addr2line -s -e codeblocks.dll 605092a0" (The module and address reported in "605092A0  C:\Program Files\CodeBlocks\codeblocks.dll:605092A0  _ZN13EditorManager5CloseEP10EditorBaseb")
4) The prompt returns with: editormanager.cpp:704 :D
5) Rinse and repeat (3) for the rest of the lines you want to decipher.

See? No need to ship debug versions ;)

Yiannis.

PS: addr2line is part of binutils IIRC and is included with the C::B/MinGW bundle.

Navigation

[0] Message Index

[#] Next page

[*] Previous page