Jump to content


Visual studio plugin - debug problems


2 replies to this topic

#1 Stainless

    Member

  • Members
  • PipPipPipPip
  • 581 posts
  • LocationSouthampton

Posted 04 July 2012 - 10:48 AM

I am having a problem with a visual studio plugin.

I have a couple of issues, the elf file for one project is over 30 meg, so it cannot just be loaded into memory.

We have a solution that parses the elf file and creates an index list, works really well. (Planning to mount the file into memory at a later date) but it has thrown up a major issue.

Visual studio does not dispose the instance of the debugger after the user finishes debugging.
It just overwrites the instance with a new instance, but we still have a reference to the elf file.

So when you try to build the app again, the elf file is locked and the build fails.

Has anyone come across this before and found a solution?

We just need some way of knowing that the user has finished debugging

#2 v71

    Valued Member

  • Members
  • PipPipPipPip
  • 353 posts

Posted 06 July 2012 - 03:14 PM

This is exaclty what keeps me well far away from plug-in s, by the way have you tried to contact the customer support ?
Check my code in the c/c++ section :
http://www.binpress.com/browse/c

#3 Stainless

    Member

  • Members
  • PipPipPipPip
  • 581 posts
  • LocationSouthampton

Posted 07 July 2012 - 11:45 AM

:D

Yes, but not a lot of use.

We have found a work around for the moment, we can detect a certain event when a debugged app closes that allows us to "guess" that we should hang up our boots





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users