| Title: | Microsoft Visual C++ bug reports and kits |
| Notice: | Register in Topic 2. 5.Last for latest Kit |
| Moderator: | DECWET::THOMAS N |
| Created: | Tue May 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 521 |
| Total number of notes: | 2938 |
Hi,
I tried msdev /p=<pid> to debug a running process.
When the msdev comes up, none of the build menu is available.
Could someone tell me what is the right way to debug a running process?
Thank you in advance,
Phung
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 516.1 | DECWET::PETERSON | Mon May 19 1997 10:56 | 11 | ||
you don't get a build menu because the running process only has
information on how to debug it, but not on how it was built.
you get a debug menu where the build menu used to be.
to get debug symbols for a running project you can copy the .pdb files
to the same directory as the images and dlls prior to running msdev
the online documentation should describe other methods for accessing
the debug information.
| |||||
| 516.2 | AXPBIZ::TRUONG | Mon May 19 1997 12:09 | 10 | ||
Hi Kim,
I took your suggestion and move the .pdb file that I want to debug
to where the .exe is. but the result is still the same.
What other steps did I miss here?
Thanks,
Phung
| |||||
| 516.3 | more info please | DECWET::PETERSON | Tue May 20 1997 10:25 | 8 | |
I don't know. Attaching to a running process is something that works
for me.
Could you write out the exact series of steps from build to run that
you took, including the directories (and machines, if any) that the
files were built in and copied to?
that might give us a clue.
| |||||