|
I would say it is possible partially.
If its a simple memory leak wherein you have allocated a pointer and left it as it is you might be able to detect in VC++.
You can remove all the breakpoints. Run the code in Debug mode(press F5) -> run the application -> close it.
Your should be able to see straightforwards leaks in the output window of the VC++ application.
If you still cant detect then you might have to use external tools like boundschecker etc in the market to detect complex memory leaks.
|
|
|
|
|
As the code is not executable, and produces dll file, I was wondering if I could do what you suggested.
TNX
|
|
|
|
|
|
nahitan wrote: I have given one big code with about 60 classes, and have been told that the code has memory leak, the code is compiled with visuall studio 6 and written in C/C++, does anybody know if the visual studio (any vresion) can find out where this emory leak would be located? Thanks
try Rational Software, they have very power Performance tools
"Opinions are neither right nor wrong. I cannot change your opinion. I can, however, change what influences your opinion." - David Crow
cheers,
Alok Gupta
VC Forum Q&A :- I/ IV
|
|
|
|
|
How can I hide the export information of my DLL, such as function name or class name?
I am seeking...
For what?
Why did you ask me for what? I don't know!
|
|
|
|
|
|
Simon.W wrote: How can I hide the export information of my DLL, such as function name or class name?
How about making the names such that only you know what they mean? I know of no other way to "hide" them, however.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
|
|
|
|
|
Simon.W wrote: How can I hide the export information of my DLL, such as function name or class name?
Its possible if you writng com.dll, you can remove tlb informatin from COM DLL, which contain the interface information and you can easily ship to end user without revealing any internal working of dll
|
|
|
|
|
Use a .def file.
For each function you export use the NONAME tag.
This will cause the function to be exported by ordinal instead of name.
This also makes the resulting dll smaller.
Exporting c++ functions (and class methods) is a pain as you have to specify the mangled name.
If you have to export a number of c++ functions/methods you may want to write a tool to generate the .def from a .map (or other such file) ... and post the tool back here. 
http://msdn2.microsoft.com/en-us/library/hyx1zcd3(VS.80).aspx[^]
...cmk
Save the whales - collect the whole set
|
|
|
|
|
Is there any utility/way that allows us to analyze all instructions in an exe file, so that instruction by instruction can be executed and analyzed. (other than commandline debug utilty in dos/windows).
|
|
|
|
|
Visual C++ decompiler for instance ?
|
|
|
|
|
Can it be used to decompile any exe?
|
|
|
|
|
i don't know for that part, but be careful anyway, it is illegal to decompile an exe that you don't own, which author specifies in its license that you cannot modify it...
|
|
|
|
|
That is not exactly true. I am going back to school and a couple of months ago we had to write a paper on software licenses. A lot of what they say is contrary to law. You can llegally reverse engineer the code for the strict purpose of improving it or fixing a bug. Of course I would not take my word for it, go and look it up yourself.
INTP
Every thing is relative...
|
|
|
|
|
OllyDBG is a good little tool for decompiling and stepping through the assembly. Though I haven't used it for a few years so there might be something better out there.
|
|
|
|
|
any disassembler/debugger could do this.. IDA, softice, win32dasm, ollydbg, vc++ debugger, windbg, ... there are many of them.
Don't try it, just do it! 
|
|
|
|
|
Does anyone know what this error is supposed to mean? I have an auto generated makefile and I don't quite know what this error means. Any help would be appreciated.
Thanks,
|
|
|
|
|
Doesn't it tell you that a separator is missing?
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
|
|
|
|
|
I think it does but I don't know where to put the separator that is missing. Any ideas? I can't tell which make file it is refrencing.
|
|
|
|
|
jonesap5 wrote: ...I don't know where to put the separator that is missing.
Between the target and the dependent.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
|
|
|
|
|
In the make file I don't know how to identify the target and the dependent and where to put it. I also don't know which make file I am placing this in. I don't know if that makes sense?
|
|
|
|
|
jonesap5 wrote: I also don't know which make file I am placing this in.
How many .mak files are there?
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
|
|
|
|
|
I look in the project directory and there is a make file, I look in the source directory and there is another Makefile. I am also wondering when it says makefile(11): fatal error U1034: syntax ..., does the 11 in parens indicate the error in on line 11 of the makefile? 
|
|
|
|
|
jonesap5 wrote: I am also wondering when it says makefile(11): fatal error U1034: syntax ..., does the 11 in parens indicate the error in on line 11 of the makefile?
Yes, and the name of the file is makefile.
"Let us be thankful for the fools. But for them the rest of us could not succeed." - Mark Twain
"There is no death, only a change of worlds." - Native American Proverb
|
|
|
|
|
So this I think is the make file and I can't see anything wrong with line 11. I even compared it to another makefile similar to this one. Can you see a problem.
RTS_HOME = C:/Program Files/Rational/Rose RealTime/C++/TargetRTS
include <$(RTS_HOME)/codegen/rtgen.mk>
MODEL = C:/ERRT/ScreenSwitchTest/ScreenSwitchTest.rtmdl
COMPONENT = "Component View::MainCapsuleTest"
RTGEN_FLAGS = -model $(MODEL) -component $(COMPONENT) -spacedeps dq
include <RTSystem/MainCapsuleTest.dep>
TARGETS = $(MainCapsuleTest_SYSTARGET)
RTGENERATE_TARGET = $(TARGETS)
RTGENERATE_DAT = rtgenerate.dat
"C:\Program Files\Microsoft Visual Studio .NET 2003\Vc7\bin\nmake.exe" /nologo
RTgenerate : $(RTGENERATE_TARGET) //my comment - is this not line 11?
.PRECIOUS : $(TARGETS)
$(MainCapsuleTest_SYSTARGET) : $(MainCapsuleTest_SYSDEPS) $(RTGENERATE_DAT)
$(RTGEN) $(RTGEN_FLAGS) -system
-- modified at 14:51 Tuesday 18th April, 2006
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
