06-07-2019, 08:37 PM
found it.
I figured it had to be something to do with access rights somewhere, so I went to the settings and checked the Securty and Privacy->Password settings. I didn't see anything odd there, but while I was in I switched to autolog on.
Guess what.. that solves it.. My projects now happily build and run and can be executed from my VisualGDB debug command.
To double check I set autologin back to off and sure enough my VisualGDB failed again
So the secret is... ensure you have automatic login, with your matching ssh username
Bizzare issue...Dunno why this is happening, but very happy I resolved it.
I figured it had to be something to do with access rights somewhere, so I went to the settings and checked the Securty and Privacy->Password settings. I didn't see anything odd there, but while I was in I switched to autolog on.
Guess what.. that solves it.. My projects now happily build and run and can be executed from my VisualGDB debug command.
To double check I set autologin back to off and sure enough my VisualGDB failed again
So the secret is... ensure you have automatic login, with your matching ssh username
Bizzare issue...Dunno why this is happening, but very happy I resolved it.
Brian Beuken
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's
Lecturer in Game Programming at Breda University of Applied Sciences.
Author of The Fundamentals of C/C++ Game Programming: Using Target-based Development on SBC's