User forums > Using Code::Blocks

Profiling a library

<< < (3/5) > >>

oBFusCATed:
The flag for symbols is -g not -G...

tigerbeard:
of course, typo. Corrected it.
Thanks

stahta01:
And, you made sure there was no "-s" that strips the debug symbols.

Tim S

BlueHazzard:
I see this also some times: For example i can not profile the code completion plugin dll of codeblocks. The symbols are simply not found, but i have them activated, because other core plugins and the wxWidgets dll work fine... Just the code completion plugin won't show me any call stack or function names...

I tried to find the reason, but was not successful. If someone is able to do it, please let me know ;)

tigerbeard:

--- Quote from: stahta01 on September 24, 2018, 06:12:26 pm ---And, you made sure there was no "-s" that strips the debug symbols.

--- End quote ---
Yes, also the huge filesize showed that the symbols were is. Optimazion was off as well


--- Quote from: BlueHazzard on September 24, 2018, 07:08:00 pm ---other core plugins and the wxWidgets dll work fine...
--- End quote ---
Do you mean you could profile one (or more) of those non-code-completion-plugins while there were running in  Codeblocks?

Navigation

[0] Message Index

[#] Next page

[*] Previous page