View previous topic :: View next topic |
Author |
Message |
DanRRight
Joined: 10 Mar 2008 Posts: 2816 Location: South Pole, Antarctica
|
Posted: Sun Sep 27, 2015 12:05 pm Post subject: Default behavior of SDGB |
|
|
When i try to run debugger from command line from the directory where MyProg.exe resides like this
C:>SDBG MyProg
***and***
the MyProg.exe also exists in other directories in the PATH (specifically in the main compiler directory) then SDBG ignores my call from my directory and takes the MyProg.exe from the one in the path. Isn't common sense telling us that's this is wrong default behavior? |
|
Back to top |
|
|
jalih
Joined: 30 Jul 2012 Posts: 196
|
Posted: Sun Sep 27, 2015 7:14 pm Post subject: Re: Default behavior of SDGB |
|
|
DanRRight wrote: | When i try to run debugger from command line from the directory where MyProg.exe resides like this
C:>SDBG MyProg
***and***
the MyProg.exe also exists in other directories in the PATH (specifically in the main compiler directory) then SDBG ignores my call from my directory and takes the MyProg.exe from the one in the path. Isn't common sense telling us that's this is wrong default behavior? |
What if you use full filename with file extension?
SDBG MyProg.exe |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2816 Location: South Pole, Antarctica
|
Posted: Sun Sep 27, 2015 8:09 pm Post subject: |
|
|
No difference |
|
Back to top |
|
|
silverfrost Site Admin
Joined: 29 Nov 2006 Posts: 191 Location: Manchester
|
Posted: Mon Sep 28, 2015 11:27 am Post subject: |
|
|
Have you tried
sdbg .\myprog,exe |
|
Back to top |
|
|
DanRRight
Joined: 10 Mar 2008 Posts: 2816 Location: South Pole, Antarctica
|
Posted: Tue Sep 29, 2015 6:22 pm Post subject: |
|
|
Looks like a hack. Easy to forget and inconvenient. I'd prefer to see the default behavior closer to the common sense and simplicity unless there is a conflict with something else |
|
Back to top |
|
|
|