digitalmars.D.announce - DDT 0.9.0 released - GDB debugging integration
- Bruno Medeiros (4/4) Nov 14 2013 DDT 0.9.0 ("Debugging is Magic") is out, see post:
- Namespace (10/12) Nov 14 2013 I get:
- Bruno Medeiros (7/16) Nov 14 2013 Hum, I think Eclipse 4.x is now the minimum Eclipse version requirement,...
- Namespace (5/24) Nov 15 2013 It works with the last version of Eclipse. But the Debugger
- Bruno Medeiros (10/30) Nov 15 2013 I'd very much welcome any reports of things that you think maybe be a
- Jacob Carlborg (4/11) Nov 16 2013 Is that a limitation in DDT/CDT?
- Bruno Medeiros (12/21) Nov 18 2013 No, there's no inherent limitation in DDT/CDT regarding that.
- Jacob Carlborg (5/14) Nov 18 2013 On Mac OS X it's no problem. I can almost mix and match 32bit and 64bit
- Alexandr Druzhinin (27/29) Nov 15 2013 I installed 4.2 version but get error again:
- Bruno Medeiros (9/39) Nov 15 2013 My bad. The effective minimum Eclipse Platform version is 4.3.0, not
- eles (3/5) Nov 15 2013 please tag it
- Ary Borenszweig (3/5) Nov 15 2013 Awesome. I like your solution for the debugger (instead of writing
- Bruno Medeiros (8/14) Nov 15 2013 Yeah, looks great, although it's not that I've done much myself, in part...
- Jacek Furmankiewicz (5/5) Nov 18 2013 Quick question: with the current version is it possible to use it
- ilya-stromberg (4/9) Nov 18 2013 Yes, manual setup is possible, but you must use absolute path
- Bruno Medeiros (5/13) Nov 19 2013 Exactly, although you can use some Eclipse resource variables in the
- ilya-stromberg (4/8) Nov 19 2013 Do you have any plans to improve this situation? For example, we
- Bruno Medeiros (9/17) Nov 20 2013 You can add that bug report yourself to Eclipse, that's pretty much
- eles (4/20) Dec 02 2013 why this?
- Bruno Medeiros (8/25) Dec 02 2013 The commit it reverted was not meant to go to master, but to a branch.
- eles (3/14) Dec 02 2013 Uf! I thought that you dropped the idea of dub support. Glad to
- Rory McGuire (4/39) Dec 02 2013 Nice. Always keeping master bug fix complete with all completed features
- Vladimir Krivopalov (20/20) Feb 11 2014 Hi Bruno,
- Bruno Medeiros (3/22) Feb 12 2014 Please follow this bug: https://github.com/bruno-medeiros/DDT/issues/43
- Vladimir Krivopalov (8/11) Feb 12 2014 Thanks for pointing me to the related bug!
- Vladimir Krivopalov (20/26) Feb 12 2014 In case when I'm using GDC 4.8.2 I'm hitting the error you've
- Bruno Medeiros (12/14) Nov 18 2013 BTW, the CDT devs are contemplating supporting LLDB as well:
- Jacob Carlborg (6/15) Nov 18 2013 Is it possible to use the GDB interface and invoke LLDB instead as the
- Bruno Medeiros (7/21) Nov 19 2013 Nah, the interface that GDB frontends use is an API for backends only
- Jacob Carlborg (4/8) Nov 19 2013 Ok, I see.
- Iain Buclaw (7/21) Nov 18 2013 Check you claims. :o)
- Bruno Medeiros (12/35) Nov 21 2013 That claim is based on the observation that the latest GDC binary
- David Nadlinger (4/8) Dec 02 2013 Finally somebody who appreciates our efforts. ;)
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
--
Bruno Medeiros - Software Engineer
Nov 14 2013
On Thursday, 14 November 2013 at 17:54:58 UTC, Bruno Medeiros
wrote:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
I get:
Cannot complete the install because of a conflicting dependency.
Software being installed: DDT - D Development Tools
0.9.0.v201311141659 (org.dsource.ddt.feature.group
0.9.0.v201311141659)
Software currently installed: Eclipse Platform
3.8.2.M20130131-0800 (org.eclipse.platform.ide
3.8.2.M20130131-0800)
Nov 14 2013
On 14/11/2013 18:46, Namespace wrote:On Thursday, 14 November 2013 at 17:54:58 UTC, Bruno Medeiros wrote:Hum, I think Eclipse 4.x is now the minimum Eclipse version requirement, due to the CDT dependency. As such, I don't think Eclipse can update itself across a major version number, so you'll need to download a new Eclipse 4.x installation. -- Bruno Medeiros - Software EngineerDDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJI get: Cannot complete the install because of a conflicting dependency. Software being installed: DDT - D Development Tools 0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659) Software currently installed: Eclipse Platform 3.8.2.M20130131-0800 (org.eclipse.platform.ide 3.8.2.M20130131-0800)
Nov 14 2013
On Thursday, 14 November 2013 at 20:02:44 UTC, Bruno Medeiros wrote:On 14/11/2013 18:46, Namespace wrote:It works with the last version of Eclipse. But the Debugger throws errors if I try to use it. Too bad. And it is even more complicated to install, than Visual D or MonoD.On Thursday, 14 November 2013 at 17:54:58 UTC, Bruno Medeiros wrote:Hum, I think Eclipse 4.x is now the minimum Eclipse version requirement, due to the CDT dependency. As such, I don't think Eclipse can update itself across a major version number, so you'll need to download a new Eclipse 4.x installation.DDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJI get: Cannot complete the install because of a conflicting dependency. Software being installed: DDT - D Development Tools 0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659) Software currently installed: Eclipse Platform 3.8.2.M20130131-0800 (org.eclipse.platform.ide 3.8.2.M20130131-0800)
Nov 15 2013
On 15/11/2013 09:02, Namespace wrote:On Thursday, 14 November 2013 at 20:02:44 UTC, Bruno Medeiros wrote:I'd very much welcome any reports of things that you think maybe be a defect with DDT (or CDT). If GDB works from the command line, it should work from Eclipse as well. A few things to watch for: Seems like a 32-bit GDB can only debug 32-bit binaries, and a 64 bit GDB can only debug 64 bit binaries. And you if you try otherwise you won't get a clear error message, so it can be confusing. -- Bruno Medeiros - Software EngineerOn 14/11/2013 18:46, Namespace wrote:It works with the last version of Eclipse. But the Debugger throws errors if I try to use it. Too bad. And it is even more complicated to install, than Visual D or MonoD.On Thursday, 14 November 2013 at 17:54:58 UTC, Bruno Medeiros wrote:Hum, I think Eclipse 4.x is now the minimum Eclipse version requirement, due to the CDT dependency. As such, I don't think Eclipse can update itself across a major version number, so you'll need to download a new Eclipse 4.x installation.DDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJI get: Cannot complete the install because of a conflicting dependency. Software being installed: DDT - D Development Tools 0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659) Software currently installed: Eclipse Platform 3.8.2.M20130131-0800 (org.eclipse.platform.ide 3.8.2.M20130131-0800)
Nov 15 2013
On 2013-11-15 17:15, Bruno Medeiros wrote:I'd very much welcome any reports of things that you think maybe be a defect with DDT (or CDT). If GDB works from the command line, it should work from Eclipse as well. A few things to watch for: Seems like a 32-bit GDB can only debug 32-bit binaries, and a 64 bit GDB can only debug 64 bit binaries. And you if you try otherwise you won't get a clear error message, so it can be confusing.Is that a limitation in DDT/CDT? -- /Jacob Carlborg
Nov 16 2013
On 16/11/2013 10:11, Jacob Carlborg wrote:On 2013-11-15 17:15, Bruno Medeiros wrote:No, there's no inherent limitation in DDT/CDT regarding that. But I was mistaken, that limitation I think is only for the GDB in the TDM-GCC suite: "You can't use a 32-bit version of GDB to debug a 64-bit program. This is why the version of GDB provided with the TDM64 edition is a 64-bit-only program. You need to use a 32-bit version of GDB, such as the one provided by the MinGW.org project, to debug 32-bit programs." http://tdm-gcc.tdragon.net/quirks I'm not sure how it is on GDB on Linux. -- Bruno Medeiros - Software EngineerI'd very much welcome any reports of things that you think maybe be a defect with DDT (or CDT). If GDB works from the command line, it should work from Eclipse as well. A few things to watch for: Seems like a 32-bit GDB can only debug 32-bit binaries, and a 64 bit GDB can only debug 64 bit binaries. And you if you try otherwise you won't get a clear error message, so it can be confusing.Is that a limitation in DDT/CDT?
Nov 18 2013
Jacob Carlborg <doob me.com> On 2013-11-18 16:37, Bruno Medeiros wrote:No, there's no inherent limitation in DDT/CDT regarding that. But I was mistaken, that limitation I think is only for the GDB in the TDM-GCC suite: "You can't use a 32-bit version of GDB to debug a 64-bit program. This is why the version of GDB provided with the TDM64 edition is a 64-bit-only program. You need to use a 32-bit version of GDB, such as the one provided by the MinGW.org project, to debug 32-bit programs." http://tdm-gcc.tdragon.net/quirks I'm not sure how it is on GDB on Linux.On Mac OS X it's no problem. I can almost mix and match 32bit and 64bit willy-nilly. -- /Jacob Carlborg
Nov 18 2013
15.11.2013 00:54, Bruno Medeiros пишет:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
I installed 4.2 version but get error again:
Cannot complete the install because of a conflicting dependency.
Software being installed: DDT - D Development Tools
0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659)
Software currently installed: Eclipse Platform 4.2.0.I20120608-1400
(org.eclipse.platform.ide 4.2.0.I20120608-1400)
Only one of the following can be installed at once:
Eclipse Workbench 3.105.0.v20130529-1406 (org.eclipse.ui.workbench
3.105.0.v20130529-1406)
Eclipse Workbench 3.103.0.v20120530-1824 (org.eclipse.ui.workbench
3.103.0.v20120530-1824)
Eclipse Workbench 3.103.1.v20120906-120042
(org.eclipse.ui.workbench 3.103.1.v20120906-120042)
Eclipse Workbench 3.105.1.v20130821-1411 (org.eclipse.ui.workbench
3.105.1.v20130821-1411)
Eclipse Workbench 3.104.0.v20130204-164612
(org.eclipse.ui.workbench 3.104.0.v20130204-164612)
Cannot satisfy dependency:
From: DDT - D Development Tools 0.9.0.v201311141659
(org.dsource.ddt.feature.group 0.9.0.v201311141659)
To: org.dsource.ddt.ide.debug [0.1.0.v201311141659]
Cannot satisfy dependency:
From: DDT Debug support (DSF) 0.1.0.v201311141659
(org.dsource.ddt.ide.debug 0.1.0.v201311141659)
To: bundle org.eclipse.ui 3.105.0
Version is the last, what should I do more?
Nov 15 2013
On 15/11/2013 08:56, Alexandr Druzhinin wrote:15.11.2013 00:54, Bruno Medeiros пишет:My bad. The effective minimum Eclipse Platform version is 4.3.0, not 4.2.0 (I've updated the DDT Installation wiki). Also, it seems as things stand Eclipse cannot update the Platform and install DDT *at the same time*, even within the same Platform major version number. So just do it in two steps, first update Eclipse ("Check for updates"), then update/install DDT. -- Bruno Medeiros - Software EngineerDDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJI installed 4.2 version but get error again: Cannot complete the install because of a conflicting dependency. Software being installed: DDT - D Development Tools 0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659) Software currently installed: Eclipse Platform 4.2.0.I20120608-1400 (org.eclipse.platform.ide 4.2.0.I20120608-1400) Only one of the following can be installed at once: Eclipse Workbench 3.105.0.v20130529-1406 (org.eclipse.ui.workbench 3.105.0.v20130529-1406) Eclipse Workbench 3.103.0.v20120530-1824 (org.eclipse.ui.workbench 3.103.0.v20120530-1824) Eclipse Workbench 3.103.1.v20120906-120042 (org.eclipse.ui.workbench 3.103.1.v20120906-120042) Eclipse Workbench 3.105.1.v20130821-1411 (org.eclipse.ui.workbench 3.105.1.v20130821-1411) Eclipse Workbench 3.104.0.v20130204-164612 (org.eclipse.ui.workbench 3.104.0.v20130204-164612) Cannot satisfy dependency: From: DDT - D Development Tools 0.9.0.v201311141659 (org.dsource.ddt.feature.group 0.9.0.v201311141659) To: org.dsource.ddt.ide.debug [0.1.0.v201311141659] Cannot satisfy dependency: From: DDT Debug support (DSF) 0.1.0.v201311141659 (org.dsource.ddt.ide.debug 0.1.0.v201311141659) To: bundle org.eclipse.ui 3.105.0 Version is the last, what should I do more?
Nov 15 2013
On Thursday, 14 November 2013 at 17:54:58 UTC, Bruno Medeiros
wrote:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
please tag it
Nov 15 2013
On 11/14/13 2:54 PM, Bruno Medeiros wrote:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
Awesome. I like your solution for the debugger (instead of writing
something from scratch). Congratulations!
Nov 15 2013
On 15/11/2013 13:29, Ary Borenszweig wrote:On 11/14/13 2:54 PM, Bruno Medeiros wrote:Yeah, looks great, although it's not that I've done much myself, in part it was mostly being lucky to have this kind of support available and being able to integrate it this way. At first I thought I might had to copy CDT's debug source code (like Descent did with JDT) and adapt it to DDT but fortunately it was not necessary. -- Bruno Medeiros - Software EngineerDDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJAwesome. I like your solution for the debugger (instead of writing something from scratch). Congratulations!
Nov 15 2013
Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...
Nov 18 2013
On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...Yes, manual setup is possible, but you must use absolute path without `~`.
Nov 18 2013
On 18/11/2013 15:32, ilya-stromberg wrote:On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:Exactly, although you can use some Eclipse resource variables in the path of linked folders. -- Bruno Medeiros - Software EngineerQuick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...Yes, manual setup is possible, but you must use absolute path without `~`.
Nov 19 2013
On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:Do you have any plans to improve this situation? For example, we can add a bug report that Eclipse doesn't support relative paths.Yes, manual setup is possible, but you must use absolute path without `~`.Exactly, although you can use some Eclipse resource variables in the path of linked folders.
Nov 19 2013
On 19/11/2013 13:29, ilya-stromberg wrote:On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:You can add that bug report yourself to Eclipse, that's pretty much independent of DDT. Personally I don't find it to be a significant limitation at all. Note that you can create an Eclipse resource variable to point to HOME, and then create linked folders relative to that variable. For example you could then link an Eclipse folder to "HOME/.dub/packages" -- Bruno Medeiros - Software EngineerDo you have any plans to improve this situation? For example, we can add a bug report that Eclipse doesn't support relative paths.Yes, manual setup is possible, but you must use absolute path without `~`.Exactly, although you can use some Eclipse resource variables in the path of linked folders.
Nov 20 2013
On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:On 18/11/2013 15:32, ilya-stromberg wrote:why this? https://github.com/bruno-medeiros/DDT/commit/b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:Exactly, although you can use some Eclipse resource variables in the path of linked folders.Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...Yes, manual setup is possible, but you must use absolute path without `~`.
Dec 02 2013
On 02/12/2013 10:35, eles wrote:On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master). -- Bruno Medeiros - Software EngineerOn 18/11/2013 15:32, ilya-stromberg wrote:why this? https://github.com/bruno-medeiros/DDT/commit/b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:Exactly, although you can use some Eclipse resource variables in the path of linked folders.Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...Yes, manual setup is possible, but you must use absolute path without `~`.
Dec 02 2013
On Monday, 2 December 2013 at 15:55:22 UTC, Bruno Medeiros wrote:On 02/12/2013 10:35, eles wrote:On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:On 18/11/2013 15:32, ilya-stromberg wrote:On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master).Uf! I thought that you dropped the idea of dub support. Glad to hear that you did not.
Dec 02 2013
Nice. Always keeping master bug fix complete with all completed features make people more likely to use tip. Another related method of managing versions that I've seen is to create forks when you want to do a release. On 2 Dec 2013 18:00, "Bruno Medeiros" <brunodomedeiros+dng gmail.com> wrote:On 02/12/2013 10:35, eles wrote:On Tuesday, 19 November 2013 at 13:15:43 UTC, Bruno Medeiros wrote:The commit it reverted was not meant to go to master, but to a branch. The idea is that master is to be kept potentially shipable at all times, and dub support is not ready (nor was it disabled in the original commit, which is another way that it could be allowed to be commited to master). -- Bruno Medeiros - Software EngineerOn 18/11/2013 15:32, ilya-stromberg wrote:why this? https://github.com/bruno-medeiros/DDT/commit/ b7a57f9e0d7915734ba6b175acfc1fd53a7a92f4On Monday, 18 November 2013 at 15:28:36 UTC, Jacek Furmankiewicz wrote:Exactly, although you can use some Eclipse resource variables in the path of linked folders.Quick question: with the current version is it possible to use it with a dub project at all (maybe via a manual project setup)? I was trying to manually set it up, pointing "sources" as the source folder and trying to get the ~/.dub/packages into the list of libraries, but it did not seem to like it...Yes, manual setup is possible, but you must use absolute path without `~`.
Dec 02 2013
Hi Bruno,
First off, I wanted to share my appreciation for working on D
support in Eclipse and especially for introducing the debugging
capabilities with DDT - really awesome!
I started playing around with the CDT debugger for D programs and
so far got a question about D dynamic arrays.
Actually they're already supported by GDB "out of box", and
indeed debugging with GDB 7.6.2 allows for the following array's
output:
<code line> int[] a = [7, 5];
(gdb) print a
$1 = {7, 5}
but still, if debugging the same code in Eclipse (CDT), I see:
a struct _Array_int {...}
length unsigned long 2
ptr int * 0x7ffff7ecdfd0
While it is definitely possible to implement some custom pretty
printers for this (and it shouldn't be that hard), I wanted to
first ask whether you have some clue about how can the D-style
array output be forced in CDT. Thanks!
Feb 11 2014
On 11/02/2014 14:53, Vladimir Krivopalov wrote:
Hi Bruno,
First off, I wanted to share my appreciation for working on D support in
Eclipse and especially for introducing the debugging capabilities with
DDT - really awesome!
I started playing around with the CDT debugger for D programs and so far
got a question about D dynamic arrays.
Actually they're already supported by GDB "out of box", and indeed
debugging with GDB 7.6.2 allows for the following array's output:
<code line> int[] a = [7, 5];
(gdb) print a
$1 = {7, 5}
but still, if debugging the same code in Eclipse (CDT), I see:
a struct _Array_int {...}
length unsigned long 2
ptr int * 0x7ffff7ecdfd0
While it is definitely possible to implement some custom pretty printers
for this (and it shouldn't be that hard), I wanted to first ask whether
you have some clue about how can the D-style array output be forced in
CDT. Thanks!
Please follow this bug: https://github.com/bruno-medeiros/DDT/issues/43
BTW, was that sample run in Linux? Using DMD?
Feb 12 2014
On Wednesday, 12 February 2014 at 11:55:00 UTC, Bruno Medeiros wrote:Please follow this bug: https://github.com/bruno-medeiros/DDT/issues/43 BTW, was that sample run in Linux? Using DMD?Thanks for pointing me to the related bug! Yes, I'm running it in Linux with GDB 7.7, DMD 2.064 and CDT 8.2.1 So far I haven't seen any errors in CDT views while running a debug session for my sample D program. Interestingly though, I don't have the "GDB MI" page under "Debug" preferences sub-tree for CDT.
Feb 12 2014
On Wednesday, 12 February 2014 at 14:23:23 UTC, Vladimir Krivopalov wrote:Yes, I'm running it in Linux with GDB 7.7, DMD 2.064 and CDT 8.2.1 So far I haven't seen any errors in CDT views while running a debug session for my sample D program. Interestingly though, I don't have the "GDB MI" page under "Debug" preferences sub-tree for CDT.In case when I'm using GDC 4.8.2 I'm hitting the error you've described in the bug: a struct int [] Error: Multiple errors reported.\ Failed to execute MI command: -var-create - * &(&(a)) Error message from debugger back end: Attempt to take address of value not located in memory.\ Failed to execute MI command: -var-create - * &(&(a)) Error message from debugger back end: Attempt to take address of value not located in memory.\ Unable to create variable object a[0] Error: Multiple errors reported.\ Failed to execute MI command: -var-create - * a[0] Error message from debugger back end: Structure has no component named operator[].\ Unable to create variable object\ Failed to execute MI command: -data-evaluate-expression a[0] Error message from debugger back end: Structure has no component named operator[].\ Failed to execute MI command: -var-create - * a[0] Error message from debugger back end: Structure has no component named operator[]. It seems that CDT attempts to apply operators & and * to D array фы * &(&(a)) and thus fails.
Feb 12 2014
On 14/11/2013 17:54, Bruno Medeiros wrote:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ
BTW, the CDT devs are contemplating supporting LLDB as well:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670
(primarily motivated by the poor support for GDB toolchain in Mac)
Nothing is decided or started yet, but it would be quite nice if they
went for it, as then LLDB support could be trivially added to DDT as
well. *fingers crossed*
Especially cool since the LDC compiler seems to be keeping up with DMD
and being up to date better than GDC (this is just my impression, I
haven't checked this claim)
--
Bruno Medeiros - Software Engineer
Nov 18 2013
On 2013-11-18 16:49, Bruno Medeiros wrote:BTW, the CDT devs are contemplating supporting LLDB as well: https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670 (primarily motivated by the poor support for GDB toolchain in Mac) Nothing is decided or started yet, but it would be quite nice if they went for it, as then LLDB support could be trivially added to DDT as well. *fingers crossed* Especially cool since the LDC compiler seems to be keeping up with DMD and being up to date better than GDC (this is just my impression, I haven't checked this claim)Is it possible to use the GDB interface and invoke LLDB instead as the executable? Just to see what happens. They're supposed to be fairly compatible. -- /Jacob Carlborg
Nov 18 2013
On 18/11/2013 20:46, Jacob Carlborg wrote:On 2013-11-18 16:49, Bruno Medeiros wrote:Nah, the interface that GDB frontends use is an API for backends only called MI (Machine Interface). It's different from the console interpreter, and LLDB does not support that: http://lists.cs.uiuc.edu/pipermail/lldb-dev/2013-February/001456.html -- Bruno Medeiros - Software EngineerBTW, the CDT devs are contemplating supporting LLDB as well: https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670 (primarily motivated by the poor support for GDB toolchain in Mac) Nothing is decided or started yet, but it would be quite nice if they went for it, as then LLDB support could be trivially added to DDT as well. *fingers crossed* Especially cool since the LDC compiler seems to be keeping up with DMD and being up to date better than GDC (this is just my impression, I haven't checked this claim)Is it possible to use the GDB interface and invoke LLDB instead as the executable? Just to see what happens. They're supposed to be fairly compatible.
Nov 19 2013
On 2013-11-19 14:17, Bruno Medeiros wrote:Nah, the interface that GDB frontends use is an API for backends only called MI (Machine Interface). It's different from the console interpreter, and LLDB does not support that: http://lists.cs.uiuc.edu/pipermail/lldb-dev/2013-February/001456.htmlOk, I see. -- /Jacob Carlborg
Nov 19 2013
On 18 November 2013 15:49, Bruno Medeiros <brunodomedeiros+dng gmail.com>wrote:On 14/11/2013 17:54, Bruno Medeiros wrote:Check you claims. :o) The only discrepancy as of writing is that Martin's work on shared library support is incompatible with, and currently blocking the 2.064 merge in GDC. -- Iain Buclaw *(p < e ? p++ : p) = (c & 0x0f) + '0';DDT 0.9.0 ("Debugging is Magic") is out, see post: https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJBTW, the CDT devs are contemplating supporting LLDB as well: https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670 (primarily motivated by the poor support for GDB toolchain in Mac) Nothing is decided or started yet, but it would be quite nice if they went for it, as then LLDB support could be trivially added to DDT as well. *fingers crossed* Especially cool since the LDC compiler seems to be keeping up with DMD and being up to date better than GDC (this is just my impression, I haven't checked this claim)
Nov 18 2013
On 18/11/2013 20:51, Iain Buclaw wrote:
On 18 November 2013 15:49, Bruno Medeiros <brunodomedeiros+dng gmail.com
<mailto:brunodomedeiros+dng gmail.com>> wrote:
On 14/11/2013 17:54, Bruno Medeiros wrote:
DDT 0.9.0 ("Debugging is Magic") is out, see post:
https://groups.google.com/d/__msg/ddt-ide/VwA7ifYt9c0/__wBcvUSVKNqMJ
<https://groups.google.com/d/msg/ddt-ide/VwA7ifYt9c0/wBcvUSVKNqMJ>
BTW, the CDT devs are contemplating supporting LLDB as well:
https://bugs.eclipse.org/bugs/__show_bug.cgi?id=405670
<https://bugs.eclipse.org/bugs/show_bug.cgi?id=405670>
(primarily motivated by the poor support for GDB toolchain in Mac)
Nothing is decided or started yet, but it would be quite nice if
they went for it, as then LLDB support could be trivially added to
DDT as well. *fingers crossed*
Especially cool since the LDC compiler seems to be keeping up with
DMD and being up to date better than GDC (this is just my
impression, I haven't checked this claim)
Check you claims. :o)
The only discrepancy as of writing is that Martin's work on shared
library support is incompatible with, and currently blocking the 2.064
merge in GDC.
--
Iain Buclaw
*(p < e ? p++ : p) = (c & 0x0f) + '0';
That claim is based on the observation that the latest GDC binary
distributable for Windows (which even so is not quite official and of
unknown stability) is based on DMD 2.060 whereas LDC has binary releases
based on 2.063.2 ...
Sure, the GDC development source maybe be more up to date to DMD, but:
a) I have no idea how stable that is. Are there even releases?
b) I find that the official GDC installation instructions for Windows
(http://www.gdcproject.org/wiki/MinGW) are way overkill, much more
hassle than should be required to install GDC.
--
Bruno Medeiros - Software Engineer
Nov 21 2013
On Thursday, 21 November 2013 at 13:56:38 UTC, Bruno Medeiros wrote:That claim is based on the observation that the latest GDC binary distributable for Windows (which even so is not quite official and of unknown stability) is based on DMD 2.060 whereas LDC has binary releases based on 2.063.2 ...Finally somebody who appreciates our efforts. ;) David
Dec 02 2013