|
Thanks all for making me realize that I was not clear in my question.
I had tried debugging before posting the question.
I placed the breakpoint inside main(). The control also stopped there when I pressed F5.
But the problem for me was that I had no idea how I could pass the commaind-line parameters
and receive it in the argv[] while debugging.
For ex :
If I could run the console application like this :
>exename commandlineparam1 commandlineparam2
How could I start the debugging for this application.
I am supposed to pass the command line params commandlineparam1 and commandlineparam1 before
starting the debugging process and I am expecting argc = 3 and argv[1] = commandlineparam1, and
so on, while debugging.
Thanks in advance
|
|
|
|
|
Open project settings There should be option for command line parameters.
Which VS version are you using?
|
|
|
|
|
Thanks for the reply.
This worked.
In VC++ 6.0, the path / flow is :
Project -> Settings -> Debug (tab) -> Program Arguments (field)
|
|
|
|
|
You are Welcome. 
|
|
|
|
|
Hi All,
I am debugging a VC++ dll,here i put a breakpoint .. but as soon as it reach to the break point it is moving to "Disassembly" that is assembly code i want to come back to the source code .. but this is not working ..
i tried with "go to source code" then it is saying source code is not avalable ...
please help me here to know how to go to the source code...
Regards,
vikas da
|
|
|
|
|
Well, you hit a routine whoose source code is not available (i.e. nothing to do pal).
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
No what ever is getting executed that is my code only... but i am seeing in assembly language ... i want to see the c++ code ...
vikas da
|
|
|
|
|
Your code uses some libraries (like the C-runtime for instance) and if the crash occurs there, then sometimes nou source code is available. Check the call stack to find one of your function that is causing the problem.
Forget what I said, I was mixing with another message 
Anyway, as already stated, you need to have the source code of the dll.
|
|
|
|
|
That's never completely true. As you can see with Dependency Walker tool, your code possibly links with several other libraries.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
tasumisra wrote: i tried with "go to source code" then it is saying source code is not avalable ...
Errh, do you have the actual source code? 
Make sure the .pdb file for dll can be found, you may copy it to the directory from which you're running the application that uses the library.
Without the .pdb file the debugger cannot find out how to map the executable code to source code and vice versa.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown
|
|
|
|
|
yes i do have .. i am executing my code only .. what was happening i was debuuging my code .. and in the meantime i modified my code so what happen it show me a pop there and there was a checkbox to show the assembly
... now it is control is going to assembly only ... not to the actual source code..
vikas da
|
|
|
|
|
tasumisra wrote: what was happening i was debuuging my code .. and in the meantime i modified my code so what happen it show me a pop there and there was a checkbox to show the assembly
Well, to me it sounds like you've built some thing with a program database for "edit and continue" and you've done just that; edited and continued.
Make sure that your .pdb file for the library is up-to-date. You may delete it and rebuild the library, or you can do a "rebuild all".
Make the rebuilds when you're not inside a debugging session.
If this has worked before, some part has got hick-ups and it's usually easily fixed by rebuilding.
"It's supposed to be hard, otherwise anybody could do it!" - selfquote
"High speed never compensates for wrong direction!" - unknown
|
|
|
|
|
It sounds like your debug settings arent complete. You got to check your project settings, to include debug information in the dll.
It is also possible that you get an assertion before your breakpoint. => Make a breakpoint at the dll startup code and than go ahead.
Greetings from Germany
|
|
|
|
|
Have you tried closing the window containing the assembly code? I've seen this often with VS6. I just close that one window and continue on.
"Love people and use things, not love things and use people." - Unknown
"To have a respect for ourselves guides our morals; to have deference for others governs our manners." - Laurence Sterne
|
|
|
|
|
|
Hello friend,
We have some aappplication which was made previously.
Actually we need to convert it into 64 bit to support the OS.
We need to use it for other aapplication which made by us in current 64 bit.
Please can anyone tell how we can convert any application(dll/exe) of 32 bit into 64 bit
abhi
|
|
|
|
|
Compile and link all your source code on 64 bit machines.
Please refer here[^] for configuring Visual C++ Projects to Target 64-Bit Platforms.
Regards,
Paresh.
|
|
|
|
|
|
I m using libtiff library which has medianfilter tool.It reduces original file(.tif) size to 1/3.Why?
|
|
|
|
|
If I understand it right the median filter is computing the difference from the median.
That leads for instance from "100 102 103" to "100 2 3" so it is shorter, and thats what you see. 
Greetings from Germany
|
|
|
|
|
Any body have sample code for "TRIVIAL FILE TRANSFER PROTOCOL" Using C++??
Thanks in Advance
Hitesh sojitra
|
|
|
|
|
|
That is a sample for FTP not TFTP.
|
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
