On Mon, 08 Mar 2010 01:54:12 -0500, Walter Bright
newshou...@digitalmars.com wrote:
Lots of meat and potatoes here, and a cookie! (spelling checker for
error messages)
http://www.digitalmars.com/d/1.0/changelog.html
http://ftp.digitalmars.com/dmd.1.057.zip
Steven Schveighoffer:
If you want to use the new release without the bugs, please apply this
patch to druntime:
http://www.dsource.org/projects/druntime/changeset?format=diffnew=262old=260new_path=trunkold_path=trunk
I have just added a small bug report, I don't know if this can interest
On Thu, 11 Mar 2010 15:20:38 -0500, bearophile bearophileh...@lycos.com
wrote:
Steven Schveighoffer:
If you want to use the new release without the bugs, please apply this
patch to druntime:
On Thu, 11 Mar 2010 15:28:36 -0500, Steven Schveighoffer
schvei...@yahoo.com wrote:
On Thu, 11 Mar 2010 15:20:38 -0500, bearophile
bearophileh...@lycos.com wrote:
Steven Schveighoffer:
If you want to use the new release without the bugs, please apply this
patch to druntime:
Steven Schveighoffer:
The compiler
would have to instrument all allocations/calls to the runtime functions
with line number arguments.
Do you suggest me to mark my bug report as Invalid then?
There's another similar bug report:
http://d.puremagic.com/issues/show_bug.cgi?id=3851
Debuggers
Steven Schveighoffer:
Also if we get exception stack trace support, then you can immediately see
everything. It's probably better to focus on that.
OK.
Do you want me to remove those two bug reports then?
Bye,
bearophile
On Thu, 11 Mar 2010 16:05:51 -0500, bearophile bearophileh...@lycos.com
wrote:
Steven Schveighoffer:
Also if we get exception stack trace support, then you can immediately
see
everything. It's probably better to focus on that.
OK.
Do you want me to remove those two bug reports then?
I
Steven Schveighoffer wrote:
If a good debugger existed for dmd, you could determine the location,
but I don't know of any good ones. gdb doesn't do a very good job with D.
dmd has produced debugging information that makes gdb choke up for ages.
This makes gdb (and some other utilities that
On Thu, 11 Mar 2010 16:14:36 -0500, grauzone n...@example.net wrote:
Steven Schveighoffer wrote:
If a good debugger existed for dmd, you could determine the location,
but I don't know of any good ones. gdb doesn't do a very good job with
D.
dmd has produced debugging information that
I did use it, ddbg worked good (but always skipped over runtime
functions, which is annoying when you are developing the runtime). I
hope that this problem eventually is solved.
Isn't ddbg totally abandoned?
stacktrace printout, there is a need for such things. But I think
exception tracing is coming, I think Tango already has it.
Tango has it since a long time. Makes me wonder why it hasn't been ported
to druntime, I thought the runtimes are quite similar.
If a good debugger existed for dmd, you could determine the location,
but I don't know of any good ones. gdb doesn't do a very good job with
D.
On Windows cv2pdb + Visual Studio works pretty damn well for me. Can't
compare it to gdb though, since I haven't used that yet.
Note to everyone, dmd 2.041 array allocation is broken (inadvertently by
my array append patch). You should not use this release.
Another big problem of the release is operator overloading.
On 11/03/10 20:28, Steven Schveighoffer wrote:
If a good debugger existed for dmd, you could determine the location,
but I don't know of any good ones. gdb doesn't do a very good job with D.
-Steve
I've never had a problem with GDB, it's always worked fine for me, for
everything I've used
Both C++ and D versions:
http://bugzilla.digitalmars.com/issues/
On 11-mar-10, at 22:09, Steven Schveighoffer wrote:
On Thu, 11 Mar 2010 16:05:51 -0500, bearophile bearophileh...@lycos.com
wrote:
Steven Schveighoffer:
Also if we get exception stack trace support, then you can
immediately see
everything. It's probably better to focus on that.
OK.
16 matches
Mail list logo
