replica nfl jerseysreplica nfl jerseyssoccer jerseyreplica nfl jerseys forums.silverfrost.com :: View topic - Debugger string length limit in VS plugin
forums.silverfrost.com Forum Index forums.silverfrost.com
Welcome to the Silverfrost forums
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Debugger string length limit in VS plugin

 
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support
View previous topic :: View next topic  
Author Message
acw



Joined: 04 Nov 2005
Posts: 165
Location: Darkest Devon

PostPosted: Fri May 01, 2009 12:44 pm    Post subject: Debugger string length limit in VS plugin Reply with quote

Hi,

This has has been around for a while. There is a limit on the number of characters you can see when watching strings in VS of around about 80 characters. This can be a bit of a pain - is there any way of getting around this (aside from adding code to print or log the string) ?

Cheers,
Alan
Back to top
View user's profile Send private message Visit poster's website
Robert



Joined: 29 Nov 2006
Posts: 457
Location: Manchester

PostPosted: Sat May 02, 2009 12:19 pm    Post subject: Reply with quote

You can usually see the rest of the string by right clicking and choosing 'Memory dump at variable'. The window it brings up should show you all the string although you will have to know where it ends.

I will look at modifying sdbg to display more of the string.
Back to top
View user's profile Send private message Visit poster's website
acw



Joined: 04 Nov 2005
Posts: 165
Location: Darkest Devon

PostPosted: Tue May 05, 2009 8:57 am    Post subject: Reply with quote

Visual Studio does not have a "memory dump at variable" option (at least not that I can see) and unfortunately the ftn95 plugin crashes if you even try to open a memory window (I also reported this problem a while ago Crying or Very sad )

The ability to use the VS memory dump window would be very very nice - I would certainly trade a working memory dump window for an increase in supported string length!

Another suggestion would be to allow a substring to be specified within the watch window (the VS C++ debugger allows this), so writing something like "mystring[50:100]" would work.

Alan
Back to top
View user's profile Send private message Visit poster's website
Robert



Joined: 29 Nov 2006
Posts: 457
Location: Manchester

PostPosted: Fri May 08, 2009 11:49 am    Post subject: Reply with quote

How do you get to the memory dump window menu entry?
Back to top
View user's profile Send private message Visit poster's website
acw



Joined: 04 Nov 2005
Posts: 165
Location: Darkest Devon

PostPosted: Fri May 08, 2009 3:17 pm    Post subject: Reply with quote

You have to be debugging something, then it's under Debug->Windows->Memory. You have four to choose from.
Back to top
View user's profile Send private message Visit poster's website
Robert



Joined: 29 Nov 2006
Posts: 457
Location: Manchester

PostPosted: Sat May 09, 2009 12:36 pm    Post subject: Reply with quote

Which VS are you using? Those window types should be turned off when debugging Win32 apps -- because they don't work Smile
Back to top
View user's profile Send private message Visit poster's website
acw



Joined: 04 Nov 2005
Posts: 165
Location: Darkest Devon

PostPosted: Mon May 11, 2009 9:27 am    Post subject: Reply with quote

2008. But the memory windows did exactly the same thing (and were accessible) in 2005.
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    forums.silverfrost.com Forum Index -> Support All times are GMT + 1 Hour
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2005 phpBB Group