locked
Switching from 32-bit Remote Debugger to 64-Bit RRS feed

  • Question

  • I am told I have the 32-bit Debugger running, and have 64-bit processes I am making.

    How do I switch?

    Wednesday, October 7, 2015 12:46 AM

All replies

  • Hi TheRedGuy1990,

    Whether this issue is related to the unit test? Do you use the VS remote debugging tool? What is your two windows Environment, 32 bit/64 bit? What is your really app, 32 bit/64 bit?

    Like Eric's suggestion here:

    https://social.msdn.microsoft.com/Forums/vstudio/en-US/3d90e300-9bee-41e5-a89f-1cf5b9516fb8/remote-debugging-x86-process-on-windows-7-x64

    We could know that the remote debugging tool still has the 32 bit and 64 bit, if you mean that you want to use the 64 bit remote debugging tool, you could install the 64 bit package in your 64 bit windows.

    If I have misunderstood this issue, please feel free to let me know.

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Wednesday, October 7, 2015 8:40 AM
  • I am using Visual Studio Community 2015.

    I cannot find a 2015 version to download.

    Do I have it already?

    Thursday, October 8, 2015 12:14 AM
  • Hi TheRedGuy1990,

    This is the Remote Tools for Visual Studio 2015:

    http://www.microsoft.com/en-us/download/details.aspx?id=48155

    You would check the detailed requirements for this remote tool.

    For example:

    Connecting to the remote debugger and profiler that are included in the Remote Tools for Visual Studio 2015 is supported in Visual Studio Enterprise 2015. 

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Thursday, October 8, 2015 3:09 AM
  • I already have the 64 bit debugger installed.

    I don't know how to switch debuggers.

    Sunday, October 11, 2015 8:56 PM
  • Do you mean that you couldn't open the X64 remote debugging tool under the VS IDE setup path?

    Reference:

    https://msdn.microsoft.com/en-us/library/ms184681.aspx

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, October 12, 2015 10:12 AM
  • Stop proposing and marking your posts to mine as answers.
    Friday, October 23, 2015 10:34 PM
  • And no.  That's not the problem.
    Friday, October 23, 2015 10:40 PM
  • Sorry for no help to you, and thanks for helping me unmark the reply.

    Actually like my first reply, the real issue would be related to what your real windows Environment and how you really debug your app.

    For example:

    Like these two documents:

    (1)https://msdn.microsoft.com/en-us/library/ms184681.aspx?f=255&MSPPError=-2147217396

    We would know that to remote debugging 64 bit process, we have to use the 64 bit debugging tool in the remote machine.

    (2)https://msdn.microsoft.com/en-us/library/bt727f1t.aspxThis document shared us how to setup the remote tool.

    If the real issue is that you want to debug a project that is built locally and then run the executable on a remote computer. I think you could get useful information here:

    https://msdn.microsoft.com/en-us/library/vstudio/8x6by8d2(v=vs.140).aspx

    Of course, the real reason why I want to know that what your two Environment are (32 bit or 64 bit) is that we couldn't install the 64 bit remote debugger tool in a 32 bit machine, and it would have the platform target requirement for 64 bit process in the specific machine(32bit/64 bit).

    If I still misunderstood this issue, please feel free to let me know,  TheRedGuy1990!

    Sincerely,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, October 26, 2015 7:42 AM
  • My machine is, i believe, 64-bit.... I vaguely remember needing 64-bit versions of other things in the past.

    I have installed both versions.  I believe I also have the x86 version if necessary.

    However, VS runs the 32-bit debugger by default.

    Thursday, October 29, 2015 7:20 PM
  • >>VS runs the 32-bit debugger by default.

    Could you share us a screen shot about this result? Where did you get the information about the 32 bit debugger?

    >>My machine is, i believe, 64-bit.... I vaguely remember needing 64-bit versions of other things in the past.

    If you local machine and the remote machine are the 64 bit Environments, do you build you app as the "platform target =X64"?

    (1)Like this thread here:

    http://stackoverflow.com/questions/16168057/remote-debugging-on-x64-windows-server-2003

    The 32 bit remote debugger tool couldn't debug the 64 bit process.

    (2)To debug the 64 bit process or dump files:

    • We need a 64-bit version of Windows
    • We need to run the 64-bit version of msvsmon.exe first

    Best Regards,

    Jack


    We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
    Click HERE to participate the survey.

    Monday, November 2, 2015 12:20 PM