Execute & debug remotely?

This is a discussion on Execute & debug remotely? within the C++ Programming forums, part of the General Programming Boards category; Originally Posted by cpjust "V:\MyProg~1.exe" Wow, we're still locked inside the 8.3 era And here I was, thinking it was ...

  1. #16
    C++まいる!Cをこわせ! Elysia's Avatar
    Join Date
    Oct 2007
    Posts
    22,170
    Quote Originally Posted by cpjust View Post
    "V:\MyProg~1.exe"
    Wow, we're still locked inside the 8.3 era
    And here I was, thinking it was standard to use non-8.3 names nowadays.
    So what makes it restricted to 8.3? It it should call itself a Windows program?
    Oh well. Good luck with it anyway. Remote debugging could have been made easier last time I checked >_<
    Quote Originally Posted by Adak View Post
    io.h certainly IS included in some modern compilers. It is no longer part of the standard for C, but it is nevertheless, included in the very latest Pelles C versions.
    Quote Originally Posted by Salem View Post
    You mean it's included as a crutch to help ancient programmers limp along without them having to relearn too much.

    Outside of your DOS world, your header file is meaningless.
    For information on how to enable C++11 on your compiler, look here.
    よく聞くがいい!私は天才だからね! ^_^

  2. #17
    and the hat of sweating
    Join Date
    Aug 2007
    Location
    Toronto, ON
    Posts
    3,545
    OK, now I'm able to step through and debug the remote .exe, but only after clicking OK to dozens of dialogs such as:
    The project 'C:\WINDOWS\system32\rpcrt4.dll' does not match the corresponding file on the remote machine.
    Is there a way to prevent it from giving me those messages and just run?

  3. #18
    Kernel hacker
    Join Date
    Jul 2007
    Location
    Farncombe, Surrey, England
    Posts
    15,677
    Are you using the same OS with the same service packs, etc? [May not be viable, but if you can, it will solve the problem].

    --
    Mats
    Compilers can produce warnings - make the compiler programmers happy: Use them!
    Please don't PM me for help - and no, I don't do help over instant messengers.

  4. #19
    and the hat of sweating
    Join Date
    Aug 2007
    Location
    Toronto, ON
    Posts
    3,545
    Quote Originally Posted by matsp View Post
    Are you using the same OS with the same service packs, etc? [May not be viable, but if you can, it will solve the problem].

    --
    Mats
    No, my dev machine is XP Pro Sp2 & remote machine is Win2003 server R2.
    Is there any way to stop those messages with different OSes?

  5. #20
    Registered User Codeplug's Avatar
    Join Date
    Mar 2003
    Posts
    4,607
    Sure - you just have to let the debugger know what DLL's you care about debugging.

    Project Settings -> Debug tab -> Category: "Addition DLLs" -> Uncheck "Try to locate other DLLs"
    Also, in the list of modules there, remove anything that you don't care about debugging, like rpcrt4.dll, ntdll.dll, user32.dll, etc, etc...

    gg

  6. #21
    CSharpener vart's Avatar
    Join Date
    Oct 2006
    Location
    Rishon LeZion, Israel
    Posts
    6,424
    You can take the used dlls from the local sytem32 dir and copy them (for debug purposes) into the folder of remote exe. It should select the dll from the current folder first - and they will be the same as on the local comp
    The first 90% of a project takes 90% of the time,
    the last 10% takes the other 90% of the time.

  7. #22
    and the hat of sweating
    Join Date
    Aug 2007
    Location
    Toronto, ON
    Posts
    3,545
    Quote Originally Posted by Codeplug View Post
    Sure - you just have to let the debugger know what DLL's you care about debugging.

    Project Settings -> Debug tab -> Category: "Addition DLLs" -> Uncheck "Try to locate other DLLs"
    Also, in the list of modules there, remove anything that you don't care about debugging, like rpcrt4.dll, ntdll.dll, user32.dll, etc, etc...

    gg
    I don't care about debugging any DLLs, I just want to step through the .exe. I unchecked everything, but that didn't help.

  8. #23
    Registered User Codeplug's Avatar
    Join Date
    Mar 2003
    Posts
    4,607
    Well, I wouldn't mess with OS dll's - trying to use XP system dll's on Server2003 may not work very well.

    End the end, there's little use for stepping-into a dll you don't have the source code for. And if you don't need to step into a dll, you can remove it from the module list under additional dll's.

    On a side note - when I have a "core dump" that I need to analyze, I use the Windows Debugger and the Microsoft Symbol Server - which will automatically download the needed symbols for any MS OS dll (which is needed for accurate stack trace sometimes). Some of my co-workers only use the windows debugger (and build off the command line) - but I'm not that "hard core"

    gg

  9. #24
    Registered User Codeplug's Avatar
    Join Date
    Mar 2003
    Posts
    4,607
    >> I unchecked everything, but that didn't help.

    Do your settings look like this?

    gg
    Attached Images Attached Images  

  10. #25
    and the hat of sweating
    Join Date
    Aug 2007
    Location
    Toronto, ON
    Posts
    3,545
    Quote Originally Posted by Codeplug View Post
    >> I unchecked everything, but that didn't help.

    Do your settings look like this?

    gg
    Well I didn't delete everything in the "modules" list, I just removed the checkmarks beside the dozens of DLLs listed there as well as the "Try to locate DLLs" box.

  11. #26
    Registered User Codeplug's Avatar
    Join Date
    Mar 2003
    Posts
    4,607
    Remove all the modules in the list and make it look like mine - then I think the popups should go away.

    gg

  12. #27
    and the hat of sweating
    Join Date
    Aug 2007
    Location
    Toronto, ON
    Posts
    3,545
    Quote Originally Posted by Codeplug View Post
    Remove all the modules in the list and make it look like mine - then I think the popups should go away.

    gg
    Hey that works!
    So then what does just unchecking them do?

  13. #28
    Registered User Codeplug's Avatar
    Join Date
    Mar 2003
    Posts
    4,607
    I'm guessing that it just prevents the loading of debug information unchecked DLLs - but doesn't prevent the warning about them not being the same across machines.

    gg

Page 2 of 2 FirstFirst 12
Popular pages Recent additions subscribe to a feed

Similar Threads

  1. Binary not built with debug info - why?
    By ulillillia in forum C Programming
    Replies: 15
    Last Post: 12-11-2008, 12:37 AM
  2. makefiles - debug & release?
    By cpjust in forum C Programming
    Replies: 6
    Last Post: 10-26-2007, 04:00 PM
  3. Debug --> Exceptions in Visual Studio 2005
    By George2 in forum C# Programming
    Replies: 1
    Last Post: 08-10-2007, 02:12 AM
  4. Results in Debug and Release mode are different
    By jaro in forum C Programming
    Replies: 11
    Last Post: 05-27-2006, 11:08 AM
  5. Ask about Debug Assert Failed
    By ooosawaddee3 in forum C++ Programming
    Replies: 0
    Last Post: 04-24-2002, 11:07 PM

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21