On 17.10.2013 08:47, evilrat wrote:
On Thursday, 17 October 2013 at 06:42:58 UTC, Rainer Schuetze wrote:
On 16.10.2013 14:33, Bruno Medeiros wrote:
* How complete is the debugging info for DMD-Win64? Is it fully
implemented, and/or are there any issues or limitations? (Rainer you are
likely
On Thursday, 17 October 2013 at 06:42:58 UTC, Rainer Schuetze
wrote:
On 16.10.2013 14:33, Bruno Medeiros wrote:
* How complete is the debugging info for DMD-Win64? Is it fully
implemented, and/or are there any issues or limitations?
(Rainer you are
likely the best to answer this one)
The s
On 16.10.2013 14:33, Bruno Medeiros wrote:
* How complete is the debugging info for DMD-Win64? Is it fully
implemented, and/or are there any issues or limitations? (Rainer you are
likely the best to answer this one)
The stock compiler does not do the replacement '@' for '.' which
confuses th
On Wednesday, 16 October 2013 at 12:33:07 UTC, Bruno Medeiros
wrote:
Feel free to add/modify the information in that page.
I've added details for the DDD frontend and the WinDbg debugger
supplied in the D compiler zip file.
On 23/09/2013 20:50, Bruno Medeiros wrote:
I'm looking to begin adding integrated debugger support for the DDT IDE
pretty soon. With this in mind it would be desirable to have a view of
what level of D language debugger support is there for the various
combinations of platform+compiler+debugger.
On 26.09.2013 14:30, Bruno Medeiros wrote:
On 26/09/2013 09:06, Rainer Schuetze wrote:
I'm not that pessimistic. Every decent debugger on Windows understands
PDB as there are standard libraries to use them. I guess they can be
used (after conveting debug information with cv2pdb for win32) as m
On 2013-09-27 12:52, Bruno Medeiros wrote:
Blocks is a C language extension by Apple. I suspect that Modules is the
same, although I couldn't google it quickly. Therefore this doesn't
really affect pure D development. Rather, it's significance would be the
same as of the use case of using Mac OS
On 26/09/2013 16:13, Jacob Carlborg wrote:
On 2013-09-26 14:22, Bruno Medeiros wrote:
Why would that be nice? It saves you the small hassle of downloading
GCC+GDB+GDC into it's own installation. With precompiled binaries for
your platform, that should take only 15 minutes of your time and then
On 2013-09-26 20:17, Iain Buclaw wrote:
I have a sneaky suspicion that it's gcc-4.1 and gdb version that works
with that compiler that is in macports. Though that is just heresay - I
don't /actually/ know.
Macports contains the GCC 4.2 - 4.9 and GDB 7.6 and GDB 6.3.50 with
Apple modification
On Sep 25, 2013 7:35 PM, "Jacob Carlborg" wrote:
>
> On Wednesday, 25 September 2013 at 14:46:20 UTC, Bruno Medeiros wrote:
>
>> Ehhh? What's up with Mac OS X and all those outdated operating system
managed installations? (I'm referring to the similar issues with had with
the JVM)
>
>
> Apple has
On 2013-09-26 14:22, Bruno Medeiros wrote:
Why would that be nice? It saves you the small hassle of downloading
GCC+GDB+GDC into it's own installation. With precompiled binaries for
your platform, that should take only 15 minutes of your time and then
you're set (well, a bit again when you want
On 26/09/2013 09:06, Rainer Schuetze wrote:
I'm not that pessimistic. Every decent debugger on Windows understands
PDB as there are standard libraries to use them. I guess they can be
used (after conveting debug information with cv2pdb for win32) as much
as Visual Studio. The visualization addons
On 25/09/2013 18:09, Sean Kelly wrote:
On Sep 25, 2013, at 7:46 AM, Bruno Medeiros
wrote:
On 24/09/2013 07:19, Jacob Carlborg wrote:
On 2013-09-23 21:50, Bruno Medeiros wrote:
(what about Mac though?)
The sate of debugging on Mac OS X is worse than on Linux. There are a
couple of problem
On Thursday, 26 September 2013 at 08:02:52 UTC, Jacob Carlborg
wrote:
On 2013-09-26 09:27, Paolo Invernizzi wrote:
I can confirm that line numbers are missing from the traces,
but at
least something like:
(lldb) b test.d:12
Breakpoint 1: where = test_dmd-head_g`D4test3mooFZi + 8,
address
On 25.09.2013 17:12, Bruno Medeiros wrote:
On 24/09/2013 07:16, Rainer Schuetze wrote:
On 23.09.2013 21:50, Bruno Medeiros wrote:
For DMD+Windows, is there only good debugger support with VisualD? :-(
And how well does that work with 32/64 bit platform variations?
Current options that I k
On 2013-09-26 09:27, Paolo Invernizzi wrote:
I can confirm that line numbers are missing from the traces, but at
least something like:
(lldb) b test.d:12
Breakpoint 1: where = test_dmd-head_g`D4test3mooFZi + 8, address =
0x000113a0
works correctly, and with tabbed autocompletatio
On 2013-09-25 16:46, Bruno Medeiros wrote:
* Line numbers don't work. Probably some issue with incorrect DWARF
generated
What are the implications? Does this mean you canr create a breakpoint
for a given source file line?
Hmm, I was wrong. Line numbers do work, including stack trace and
br
On Wednesday, 25 September 2013 at 18:34:14 UTC, Jacob Carlborg
wrote:
On Wednesday, 25 September 2013 at 14:46:20 UTC, Bruno Medeiros
wrote:
What are the implications? Does this mean you canr create a
breakpoint for a given source file line?
I have tried that. But want I do know is that th
On Wednesday, 25 September 2013 at 14:38:27 UTC, Iain Buclaw
wrote:
On 25 September 2013 14:45, Bruno Medeiros
Perhaps I described it incorrectly then. What I mean is that
most references
and displays of D symbols are made using proper D names, and
not mangled
names (as you might get if you run
On Wednesday, 25 September 2013 at 18:34:14 UTC, Jacob Carlborg
wrote:
I have tried that.
Should have been: I haven't tried that.
--
/Jacob Carlborg
On Wednesday, 25 September 2013 at 17:09:32 UTC, Sean Kelly wrote:
Probably. But it would be nice if this worked with the
compiler that ships with OSX. And for what it's worth, "gcc"
on OSX isn't GCC any more either. It's a wrapper around the
LLVM C compiler.
Technically it's the GCC fron
On Wednesday, 25 September 2013 at 14:46:20 UTC, Bruno Medeiros
wrote:
Ehhh? What's up with Mac OS X and all those outdated operating
system managed installations? (I'm referring to the similar
issues with had with the JVM)
Apple has abandoned the GCC tool chain. They're betting all on
the
On Sep 25, 2013, at 7:46 AM, Bruno Medeiros
wrote:
> On 24/09/2013 07:19, Jacob Carlborg wrote:
>> On 2013-09-23 21:50, Bruno Medeiros wrote:
>>
>>> (what about Mac though?)
>>
>> The sate of debugging on Mac OS X is worse than on Linux. There are a
>> couple of problems:
>>
>> * D symbols ne
On 24/09/2013 07:16, Rainer Schuetze wrote:
On 23.09.2013 21:50, Bruno Medeiros wrote:
For DMD+Windows, is there only good debugger support with VisualD? :-(
And how well does that work with 32/64 bit platform variations?
Current options that I know of for Windows:
- DMD/Win32+windbg(1996):
On 24/09/2013 07:19, Jacob Carlborg wrote:
On 2013-09-23 21:50, Bruno Medeiros wrote:
(what about Mac though?)
The sate of debugging on Mac OS X is worse than on Linux. There are a
couple of problems:
* D symbols need to be prefixed with an extra underscore
* The GDB system debugger is very
On 25 September 2013 14:45, Bruno Medeiros
wrote:
> On 23/09/2013 23:57, Iain Buclaw wrote:
>>
>> On 23 September 2013 20:50, Bruno Medeiros
>> wrote:
>>>
>>> I'm looking to begin adding integrated debugger support for the DDT IDE
>>> pretty soon. With this in mind it would be desirable to have a
On 25/09/2013 14:45, Bruno Medeiros wrote:
Perhaps I described it incorrectly then. What I mean is that most
references and displays of D symbols are made using proper D names, and
not mangled names (as you might get if you run it through a pure C/C++
debugger). I've haven't yet seen something li
On 23/09/2013 23:57, Iain Buclaw wrote:
On 23 September 2013 20:50, Bruno Medeiros
wrote:
I'm looking to begin adding integrated debugger support for the DDT IDE
pretty soon. With this in mind it would be desirable to have a view of what
level of D language debugger support is there for the var
On 24/09/2013 14:42, eles wrote:
On Monday, 23 September 2013 at 23:45:12 UTC, eles wrote:
On Monday, 23 September 2013 at 19:50:35 UTC, Bruno Medeiros wrote:
OTOG, simple quetsion: how to install/update DDT plugin to the git
HEAD version?
Found that. Could you, please, tag the different relea
On 24 September 2013 19:14, Joseph Rushton Wakeling
wrote:
> On 24/09/13 19:28, Iain Buclaw wrote:
>>>
>>> ... are we talking about the same mangling issue here?
>>
>>
>> What dmd does is not the same as gdc... :)
>
>
> I wondered if you'd inherited something from the frontend ... :-)
>
Debugging
On 24/09/13 19:28, Iain Buclaw wrote:
... are we talking about the same mangling issue here?
What dmd does is not the same as gdc... :)
I wondered if you'd inherited something from the frontend ... :-)
On 24 September 2013 18:19, Joseph Rushton Wakeling
wrote:
> On 24/09/13 00:57, Iain Buclaw wrote:
>>
>> GDB doesn't understand D mangling. We currently leverage the use of
>> setting pretty-print names for debugging purposes, but you require to
>> put the names in 'quotation.marks' - I will fix
On 24/09/13 00:57, Iain Buclaw wrote:
GDB doesn't understand D mangling. We currently leverage the use of
setting pretty-print names for debugging purposes, but you require to
put the names in 'quotation.marks' - I will fix this sometime this
year... maybe. :)
When I asked about the possibilit
On 24 September 2013 14:31, Wyatt wrote:
> On Monday, 23 September 2013 at 22:57:27 UTC, Iain Buclaw wrote:
>>
>>
>> GDB doesn't understand D mangling. We currently leverage the use of
>> setting pretty-print names for debugging purposes, but you require to
>> put the names in 'quotation.marks' -
On Monday, 23 September 2013 at 23:45:12 UTC, eles wrote:
On Monday, 23 September 2013 at 19:50:35 UTC, Bruno Medeiros
wrote:
OTOG, simple quetsion: how to install/update DDT plugin to the
git HEAD version?
Found that. Could you, please, tag the different releaseed
versions, it is helpful whe
On Monday, 23 September 2013 at 22:57:27 UTC, Iain Buclaw wrote:
GDB doesn't understand D mangling. We currently leverage the
use of
setting pretty-print names for debugging purposes, but you
require to
put the names in 'quotation.marks' - I will fix this sometime
this year... maybe. :)
Ah
On 2013-09-23 21:50, Bruno Medeiros wrote:
(what about Mac though?)
The sate of debugging on Mac OS X is worse than on Linux. There are a
couple of problems:
* D symbols need to be prefixed with an extra underscore
* The GDB system debugger is very old. It doesn't have the D patches the
u
On 23.09.2013 21:50, Bruno Medeiros wrote:
For DMD+Windows, is there only good debugger support with VisualD? :-(
And how well does that work with 32/64 bit platform variations?
Current options that I know of for Windows:
- DMD/Win32+windbg(1996): This is a version of windbg from 1996 with
On Monday, 23 September 2013 at 19:50:35 UTC, Bruno Medeiros
wrote:
Is debugger support with DMD+Linux+GDB as good as it is with
GDC?
I could test with GDC and DMD on Linux (for GDB).
OTOG, simple quetsion: how to install/update DDT plugin to the
git HEAD version?
On 23 September 2013 20:50, Bruno Medeiros
wrote:
> I'm looking to begin adding integrated debugger support for the DDT IDE
> pretty soon. With this in mind it would be desirable to have a view of what
> level of D language debugger support is there for the various combinations
> of platform+compi
I'm looking to begin adding integrated debugger support for the DDT IDE
pretty soon. With this in mind it would be desirable to have a view of
what level of D language debugger support is there for the various
combinations of platform+compiler+debugger.
This information would be quite benefici
What about Win64 and VS Debugger?
42 matches
Mail list logo