Hi there, Is it possible to "attach to process" in Intel Insepector 2011 XE for windows in vs2005?
attach to process in Intel Inspector 2011 XE for windows in VS2005
ven, 17/08/2012 - 12:17
attach to process in Intel Inspector 2011 XE for windows in VS2005
Reportez-vous à notre Notice d'optimisation pour plus d'informations sur les choix et l'optimisation des performances dans les produits logiciels Intel.
- Identifiez-vous pour poster des commentaires
sam, 18/08/2012 - 18:22
No. attaching feature is only for Intel? VTune™ Amplifier XE.
Thinking that the tool have to know memory allocation from application's launching...then know leaks, I suppose.
Regards, Peter
- Identifiez-vous pour poster des commentaires
lun, 20/08/2012 - 11:20
was wonderinf if there is some way to analyse the memory leak / error for multithreaded dlls. In my case some third party application used to load the dll's. Earlier we use memory validator to find out the memory leak in single threaded dll. It allows to attach to the process and we attach from the moment we start the gui / process. It would be very nice if there is something like this in inspector.
- Identifiez-vous pour poster des commentaires
lun, 20/08/2012 - 20:37
Let me clarify on multithreaded dlls used:
1. If your application will usethird party application by loading dlls, Inspector XE can detect all memory leaks occurred in these dlls.
2. If your application will use third party application by creating a new (child) process, Inspector XE cannot detect them.
Remember that Inspector XE only works for a single process.
Regards, Peter
- Identifiez-vous pour poster des commentaires
mer, 22/08/2012 - 11:54
I tried to wrote "sample application.exe" which use system call to start thrid party gui application. Third party gui appliation will load my multithreaded dll. I executed this way and everythings work fine. Now I used Intel inspector 2011 XE to start "sample application.exe" and when my third party gui loads my multithreaded dll, i am getting "Invalid access to memory location (998)". I dont see this error if I don't use Intel Inspector. This occurs only when I use it with intel inspector.
- Identifiez-vous pour poster des commentaires
mer, 22/08/2012 - 18:58
I think that you may write a script which launches "sample application.exe" - it system-calls 3rd-party app which calls your dlls. Then use - (for example)
"inspxe-cl -collect mi3 -executable-of-interest your-dll -- my.sh".
Note that you launched "sample application.exe" as target app, which was not in same process memory space of 3rd-party application.
- Identifiez-vous pour poster des commentaires
mar, 25/09/2012 - 02:33
Hi there,
I am using Intel Inspector XE 2013 for memory leak analysis.
My requirement is like mentioned below:
My exe is spawning to many child process.
I want to analyze each of the child process at run time.
Unfortunatly I am not able to see any "attach process" option in Inspector.
Kindly let me know the way I can fulfil my purpose.
Thanks in advance.
Regards,
Krupesh D