Sysprogs forums › Forums › VisualGDB › Illegal characters in path
- This topic has 4 replies, 2 voices, and was last updated 5 years, 8 months ago by support.
-
AuthorPosts
-
August 31, 2018 at 09:01 #21857ElsonParticipant
Hi,
When debugging Android command line program, the following error message (please see the figure
below) often is displayed (sometimes it doesn’t display, so wired!). Also, I found all exit codes
are 0, and I guess 0 means a clean exit without any errors, right?Could you give some tips to avoid this error message reappear?
- This topic was modified 5 years, 8 months ago by Elson.
Attachments:
You must be logged in to view attached files.August 31, 2018 at 22:54 #21863supportKeymasterHi,
Most likely VisualGDB fails to process some path reported by one of the internal components. Please try downloading VisualGDB 5.4 Preview 4 and then check the View->Other Windows->VisualGDB Diagnostics Console for detailed exception traces. Please let us know the stack trace shown there and we should be able to fix this, or suggest a workaround.
September 1, 2018 at 14:08 #21865ElsonParticipantThe exception trace is as follows,
[+124 msec] Got DTE
[+124 msec] Got MCS
[+128 msec] Got services
[+1925 msec] Checking fonts/colors
[+1965 msec] Checked fonts/colors
[+1965 msec] Checking out features
[+2000 msec] Checked out features
[+2570 msec] Constructed Add-in
[+2581 msec] Loading settings…
[+2582 msec] Loaded settings.
[+2582 msec] Created normal commands
[+2591 msec] Created context commands
[+2594 msec] Created combo commands
[+2596 msec] Created drop down commands
[+2599 msec] Registered commands
[+6394 msec] Startup project reset
[+6471 msec] Settings validated
[+7235 msec] Startup project set
Creating a SuggestedActionsSource for D:\test\jni\Androidcmd.c…
Creating a SuggestedActionsProvider for D:\test\jni\Androidcmd.c…
No backend client found. Could not create the SuggestedActionsProvider
Rebuild all adornments: 16 msec
Searching for active configuration for jni\Androidcmd.vcxproj…
Trying fast lookup…
Found! Configuration name = Debug
Searching for active configuration for jni\Androidcmd.vcxproj…
Trying fast lookup…
Found! Configuration name = Debug
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe devices
List of devices attached
emulator-5554 deviceCommand exited with code 0
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s emulator-5554 shell getprop ro.product.cpu.abi
armeabi-v7aCommand exited with code 0
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s emulator-5554 shell getprop ro.build.version.sdk
23Command exited with code 0
September 2, 2018 at 03:19 #21868ElsonParticipantIf I debug this program again, the exception trace only includes the following info,
Searching for active configuration for jni\Androidcmd…
Trying fast lookup…
Found! Configuration name = Debug
Searching for active configuration for jni\Androidcmd…
Trying fast lookup…
Found! Configuration name = Debug
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe devices
List of devices attached
emulator-5554 deviceCommand exited with code 0
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s emulator-5554 shell getprop ro.product.cpu.abi
armeabi-v7aCommand exited with code 0
C:\Program Files (x86)\Android\android-sdk\platform-tools\adb.exe -s emulator-5554 shell getprop ro.build.version.sdk
23Command exited with code 0
September 2, 2018 at 18:45 #21871supportKeymasterHi,
Sorry about that, looks like the proper exception trace for this case wasn’t saved correctly. Please try this build and attach the updated trace: http://sysprogs.com/files/tmp/VisualGDB-5.4.4.2417.msi
-
AuthorPosts
- You must be logged in to reply to this topic.