Advertisement

Improving string output for debugger?

Started by August 14, 2011 11:35 AM
3 comments, last by Friggle 13 years, 3 months ago
Hi,

any hints on how the debugger add-on output could be improved for strings (not only printing the address but the string content)?

Many thanks!
Hi,

the idea is that the application would derive from the CDebugger add-on to add the application specific implementation, i.e. how to represent application registered types in the debugger.

I'll plan to improve the asrun sample to show how this can be done.

Regards,
Andreas

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Advertisement
the idea is that the application would derive from the CDebugger add-on to add the application specific implementation, i.e. how to represent application registered types in the debugger. [/quote]
Yes, I already do so in my app. The challenge for me is not how the representation in my app could be done but how I can determine in my debugger code that the parsed variable actually is a string.

Is this a simple thing to post here or should I wait until your asrun example is expanded?

Many thanks and regards
That is quite easy:



asIObjectType *type = engine->GetObjectTypeById(typeId);
if( strcmp(type->GetName(), "string") == 0 )
{
s << *(string*)value;
}

AngelCode.com - game development and more - Reference DB - game developer references
AngelScript - free scripting library - BMFont - free bitmap font generator - Tower - free puzzle game

Thanks a lot!

Regards

This topic is closed to new replies.

Advertisement