- This topic has 5 replies, 2 voices, and was last updated 7 years ago by
.
-
Posts
-
Hi,
I would like to know if VisualGDB can be used setting a OSX system as target. OSX is POSIX compliant and has all the same tools used in linux for debugging (GDB, gdbserver,…).
If this is currently not supported, do you plan to implement it any time soon?
Thank you
Hi,
As MacOS is different from Linux in many ways, is much less popular among our users and often introduces breaking changes, we don’t guarantee that VisualGDB will support the latest version out-of-the-box (although it automatically detects and applies a few workarounds).
Our best advice would be to try installing gdb from macports and configuring VisualGDB to use it. If this doesn’t work, please post the details here and we will walk you through setting it up.
Hi,
I got the latest GDB version installed from sources in the OSX system:
defaults-Mac:~ default$ gdb GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-apple-darwin17.0.0". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". (gdb)
But when I try to connect with the remote server creating a project it says it can find gdb and it can’t install it (VisualGDB tries to use apt-get and yum).
I did create the project anyway and select the gdb path at MSBuild Settings with custom toolchain but I get this error:
VisualGDB version: 5.2.15.1452 ------------------ System.Reflection.TargetInvocationException ------------------ System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> System.Exception: Failed to detect GCC specs at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.RunAction[_ResultType](ph1`1 action, String title, String caption, o2 exceptionHandler, Int32 noFormTimeout, String[] stages) at ji1.a[_ResultType](ph1`1 b, String e, String d, o2 c, Int32 f, String[] a) at zd.f2.o3`1.g() at sd1.x`1.d(Object a) --- End of inner exception stack trace --- at sd1.o1[_Type](e`1 a) at zd.f2.d3[_ResultType](ph1`1 c, String b, Int32 d, String[] a) at zh1.b(ToolchainDefinition d, hr1 c, uy b, Boolean a) at j41.m.a(rn1 b, IVCConfiguration c, Boolean& a) at j41.w(rn1 b, IVCConfiguration e, ToolchainDefinition a, hr1 d, uy c) at j41.d_2(vn1 b, Object a) at lt.p1(rn1 b, IVCConfiguration a) at c31.l1(String a, rn1 b, IVCConfiguration c, Boolean e, it d) at ib1.i1(Boolean a, it b) ------------------ Inner exception ------------------ ------------------ System.Exception ------------------ System.Exception: Failed to detect GCC specs at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.RunAction[_ResultType](ph1`1 action, String title, String caption, o2 exceptionHandler, Int32 noFormTimeout, String[] stages) at ji1.a[_ResultType](ph1`1 b, String e, String d, o2 c, Int32 f, String[] a) at zd.f2.o3`1.g() at sd1.x`1.d(Object a)
What should I do?
Thanks!
Hi,
We have just rechecked everything on the latest MacOS High Sierra and could not reproduce the problem with the gcc specs. The project got created fully automatically, although debugging was not possible because MacOS High Sierra does not have a compatible gdb build yet.
We would advise trying an earlier MacOS build and also updating to VisualGDB 5.3R6 (looks like you are using the previous v5.2).
I need t use debugging. What OSX version should I use to do debugging?
Thanks guys! The VisualGDB support is one of the best i’ve ever had.
Hi,
We are sorry for the inconvenience. Unfortunately Apple is known for not maintaining backward compatibility for 3rd-party tools like gdb, so we cannot promise that gdb won’t be broken by a recent update to any other OS X version. We would advise trying Mac OS 10.12 Sierra (as long as you can debug your program with gdb via command line, VisualGDB should support it as well).
- You must be logged in to reply to this topic.