Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
RE: [cdt-dev] Launch

Maybe you can do something similar for DSF-GDB?
In dsf.gdb.ui/plugin.xml we define an extension to CDebugger which calls dsf.gdb.ui.GdbDebuggerPage and that is where
IGDBLaunchConfigurationConstants.ATTR_DEBUG_NAME is set.  If you can set this one to the full path of GDB, then you should
be in business.

From: cdt-dev-bounces@xxxxxxxxxxx [cdt-dev-bounces@xxxxxxxxxxx] On Behalf Of Doug Schaefer [cdtdoug@xxxxxxxxx]
Sent: February 4, 2010 9:21 PM
To: CDT General developers list.
Subject: Re: [cdt-dev] Launch

On Thu, Feb 4, 2010 at 8:53 PM, Marc Khouzam <marc.khouzam@xxxxxxxxxxxx<mailto:marc.khouzam@xxxxxxxxxxxx>> wrote:
Hi Doug,

I'm not very familiar with the CDI launch stuff, so I'm not sure I understand what you are trying to do.

The way I launch DSF-GDB on Windows is:
1- download MinGw GDB and put it somewhere
2- add 'somewhere' to my PATH so gdb can be found without an absolute path
2- choose any of the C/C++ launch configurations (like C/C++ Local Application)
3- choose project and binary and press debug.  gdb will be found automatically since it's in my PATH.
  (of course, you can specify whichever gdb location you want in the 'debugger' tab of the launch, if you prefer)

But I'm guessing you are trying to do more than that?

Yeah, I'm trying to make it easy for Windows developers who may not even know what gdb is, by setting up the path for them.


From: cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx> [cdt-dev-bounces@xxxxxxxxxxx<mailto:cdt-dev-bounces@xxxxxxxxxxx>] On Behalf Of Doug Schaefer [cdtdoug@xxxxxxxxx<mailto:cdtdoug@xxxxxxxxx>]
Sent: February 4, 2010 3:31 PM
To: CDT General developers list.
Subject: [cdt-dev] Launch

Anyway :). I'm going to stick to technical issues here for a while.

I just tried gdb 7.0.1 for mingw and it seems to work fine. I'll focus on that for the next little while and see how it goes.

Now, for the last incarnation of Wascana, I created a MinGW debugger for CDI that managed finding the gdb executable. I did that by defining a CDebugger that subclassed the GDBDebugger and the set the buildIdPattern element in the CDebugger extension to refer to the mingw toolchain. In a somewhat hokey manner, the launch shortcut and the debugger tab picked the default CDebugger based on the active build configuration that way, and everything just magically worked.

I'm hoping to do the same for DSF/GDB. Any hints at where I should start?


BTW, does the Windows gdb 7 support all the same fancy features as on Linux? In my early investigation of 7, there seemed to be some features that weren't supported.
cdt-dev mailing list

Back to the top