Unable to debug.... release.exe....why ?

I am trying to debug my component in the release mode (I have included debug info into the exe)
I compile the code on one machine (i can debug the same there)
Then i copy the exe to another machine where i need to debug it. But when i try to debug it there, the break points get disabled (no symbols are loaded)... and i cant debug my component.

Why are the break points getting disabled ?
In the past I used to copy the code, and compile it on that machine where i want to debug and then it words. I dont have the option to copy since i need to copy a lot of data to do that.

I would like to know why is this happening?

I suspect that you have wrong version of PDB file on remote computer.
If you can debug release version on your development machine then certainly you should be able to do it on remote, try copying the PDB file along with the DLL/EXE to remote computer.

I never tried this .but if you want why not you Simply go with MessageBox() which will Pretty fast and help you to resolve your problem.

Thanx

I wasnt copying the pdb file. I did not know about it. Will read bout it.

I see that the description in file view says, it holds debug info in that. I was under the impression that all gets into the exe itself.

thanks

Quote:

---

Originally Posted by humptydumpty

I never tried this .but if you want why not you Simply go with MessageBox()

---

Do you place MessageBox all where in code to just detect some problem ?

Whats if your program even dont crash and gives no clue of what the hell is happening.

Quote:

---

which will Pretty fast and help you to resolve your problem.

---

Is it ?

Quote:

---

Originally Posted by humptydumpty

I never tried this .but if you want why not you Simply go with MessageBox() which will Pretty fast and help you to resolve your problem.

---

hmmm..... then what is the need of a debugger??? ;)


I prefer to use debugger... much easier and very helpful in debugging

Quote:

---

Originally Posted by Vedam Shashank

I wasnt copying the pdb file.

---

The only reason you get breakpoints disabled is that you dont have source code and the output DLL and/or PDB in sync. If you recompile the project then you must replace the DLL on target system to get both in sync.

Can you explain a bit on what steps you perform to debug it ?

Only Few TImes My Code Create Problem in release Mode. Till Now I didn't face any of the Problem in release mode.yes dependency can be a Problem but Error Don't think they would like to see me in Release mode. That's Why i don't want a Debugger in release mode. Will Suggest you check your code in debug version on the machine and i am sure that you will defe get the error on the machine . See Dude use exception handling in your code .And one Good way is if your are doing some big Project so make a Log File. Which Will tell you where and when and on which Place you get the error.OtherWise if this carshes on client machine how will you come to know on which place your program crash. Don't Think you will go to client machine to debug your code.so better avoid memory leak and Logical Error in your program so atleast if it will work proper in debug mode. then with minute modefication will also run proper in release mode

Thanx

Quote:

---

Originally Posted by Krishnaa

The only reason you get breakpoints disabled is that you dont have source code and the output DLL and/or PDB in sync. If you recompile the project then you must replace the DLL on target system to get both in sync.

Can you explain a bit on what steps you perform to debug it ?

---

I installed the software....then I built the exe with debug info. I copied the exe, but not the pdb file. Thats y i was not able to debug. Once i copied the pdb file all was fine.


One other question....
This is how I debug,

• Install the software on the test machine.
• Install Visual studio (this is a pain... consumes too much of time)
• Then copy the required dll/exe with debug info to start debugging.

Is there any way to debug on a test machine, without having to install visual studio.

Quote:

---

Originally Posted by Vedam Shashank

Is there any way to debug on a test machine, without having to install visual studio.

---

http://www.microsoft.com/whdc/devtoo...g/default.mspx

Regards,

Paul McKenzie

Quote:

---

Originally Posted by Vedam Shashank

I installed the software....then I built the exe with debug info. I copied the exe, but not the pdb file. Thats y i was not able to debug. Once i copied the pdb file all was fine.


One other question....
This is how I debug,

• Install the software on the test machine.
• Install Visual studio (this is a pain... consumes too much of time)
• Then copy the required dll/exe with debug info to start debugging.

Is there any way to debug on a test machine, without having to install visual studio.

---

I thought you are already remote debugging :), anyway if the target computer is accessible from Development computer then it's easy to remote debug using Visual Studio .NET, you can attach to remote process using Debug->Process->Specify IP and attach.

You need to copy MSVCMON and it's dependancies to target computer and run it in Native mode(TCP-IP mode) using command line as,

Quote:

---

msvcmon.exe -tcpip -anyuser -timeout -1

---

This will let any user (even if who dont have permission to read on target comp.) to debug.

It's also possible with VC++ 6 with almost same steps, but you can not attach to remote process, you need to start debugging using F5.

http://www.nachreiner.com/remotedebug/
http://www.codeproject.com/debug/remotedebug.asp

http://msdn.microsoft.com/library/en...asp?frame=true

Quote:

---

Originally Posted by Paul McKenzie

http://www.microsoft.com/whdc/devtoo...g/default.mspx

Regards,

Paul McKenzie

---

Havent been able to look into it...very busy....ahhhhh...

but will definately later
Thanks

Quote:

---

Originally Posted by Krishnaa

I thought you are already remote debugging :), anyway if the target computer is accessible from Development computer then it's easy to remote debug using Visual Studio .NET, you can attach to remote process using Debug->Process->Specify IP and attach.

---

Was not able to remote debug.... i thought i will go back to that once i am a little free.... could not afford to loose time :(....

had someone manually install Visual studio on the remote machine.....

thanks 4 ur help
definately appreciate it
:thumb: