User forums > Using Code::Blocks
Profiling a library
tigerbeard:
Tried to profile the DLL with VerySleepy. I compiles the DLL with the profile compile switch enabled. in release mode.
The started the Base application from wxSleepy, giving the Apps working directory.
VerySleepy does record stuff while the application runs and after its closed it shows results.
But there are no data except Baseapplcation OS calls and OS module call, nothing specific to the DLL. No link to any function names etc.
So I would conclude you can not use VerySleepy for that purpose
BlueHazzard:
You have to compile the dll with debug symbols, not with profiler settings enabled. Any profiler needs debug symbols in the binary to give you function names ecc...
tigerbeard:
Tried that but it made no difference, same result.
stahta01:
--- Quote from: tigerbeard on September 23, 2018, 11:32:19 pm ---Tried that but it made no difference, same result.
--- End quote ---
So, you compiled the DLL with debug symbols; but, failed to get more information, correct?
Tim S.
tigerbeard:
Right. I did compile the DLL with -g compiler switch and with/without -pg switch and run its executable with VerySleepy.
I did not see a single list entry with a function from the DLL, even though I could verifiy it was definitely executed.
Did you manage to profile a DLL with VerySleepy before?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version