Re: Article: Finding memory bugs in D code with AddressSanitizer

2018-01-04 Thread codephantom via Digitalmars-d-announce
On Friday, 5 January 2018 at 01:32:50 UTC, Walter Bright wrote: On 1/3/2018 4:46 PM, Walter Bright wrote: On 1/3/2018 3:16 PM, Martin Nowak wrote: https://issues.dlang.org/show_bug.cgi?id=18190 This is a stack overflow caused by having 4096 expression statements. The compiler joins them with

Re: Article: Finding memory bugs in D code with AddressSanitizer

2018-01-04 Thread Walter Bright via Digitalmars-d-announce
On 1/3/2018 4:46 PM, Walter Bright wrote: On 1/3/2018 3:16 PM, Martin Nowak wrote: https://issues.dlang.org/show_bug.cgi?id=18190 This is a stack overflow caused by having 4096 expression statements. The compiler joins them with a commaexpression, and then recursively traverses it. > Nothi

Re: Article: Finding memory bugs in D code with AddressSanitizer

2018-01-04 Thread Johan Engelen via Digitalmars-d-announce
On Wednesday, 3 January 2018 at 23:16:45 UTC, Martin Nowak wrote: On 12/25/2017 06:03 PM, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html Just built dmd with

Re: Article: Finding memory bugs in D code with AddressSanitizer

2018-01-03 Thread Walter Bright via Digitalmars-d-announce
On 1/3/2018 3:16 PM, Martin Nowak wrote: https://issues.dlang.org/show_bug.cgi?id=18190 This is a stack overflow caused by having 4096 expression statements. The compiler joins them with a commaexpression, and then recursively traverses it. > Nothing in the D part, not too surprising given d

Re: Article: Finding memory bugs in D code with AddressSanitizer

2018-01-03 Thread Martin Nowak via Digitalmars-d-announce
On 12/25/2017 06:03 PM, Johan Engelen wrote: > I've been writing this article since August, and finally found some time > to finish it: > > http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html Just built dmd with AddressSanitizer and ran dmd's, druntime's, and phobos' test-s

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-29 Thread Atila Neves via Digitalmars-d-announce
On Thursday, 28 December 2017 at 16:29:49 UTC, Johan Engelen wrote: On Monday, 25 December 2017 at 17:03:37 UTC, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.htm

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-28 Thread Johan Engelen via Digitalmars-d-announce
On Monday, 25 December 2017 at 17:03:37 UTC, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html Is it a good fit with /r/programming ? -Johan

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-26 Thread Johan Engelen via Digitalmars-d-announce
On Tuesday, 26 December 2017 at 22:11:18 UTC, Jon Degenhardt wrote: On Monday, 25 December 2017 at 17:03:37 UTC, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.htm

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-26 Thread Walter Bright via Digitalmars-d-announce
I posted this on another thread. It succinctly points out what is the fundamental difference between C++ and D on memory safety: C++: int foo(int* p) { return p[1]; } int bar(int i) { return foo(&i); } clang++ -c test.cpp -Wall D: @safe: int foo(int* p) { return p[1]; }

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-26 Thread Jon Degenhardt via Digitalmars-d-announce
On Monday, 25 December 2017 at 17:03:37 UTC, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html "LDC comes with improved support for Address Sanitizer since the

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-26 Thread Mengu via Digitalmars-d-announce
On Tuesday, 26 December 2017 at 08:03:44 UTC, Temtaime wrote: The main font is very ugly. Code font looks ok tw. on the contrary, post font is very readable (might use some letter spacing), clear and beautiful. that is on a retina macbook pro. code blocks are very readable too.

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-26 Thread Temtaime via Digitalmars-d-announce
The main font is very ugly. Code font looks ok tw.

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Walter Bright via Digitalmars-d-announce
On 12/25/2017 3:17 PM, Johan Engelen wrote: On Monday, 25 December 2017 at 20:31:18 UTC, Walter Bright wrote: Thanks for the great article! Some suggestions: Thanks for your comments, I've incorporated them (to my liking). 1. The gray-on-white text is not very legible. Looks great here, I

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Ali Çehreli via Digitalmars-d-announce
On 12/25/2017 09:03 AM, Johan Engelen wrote: Thanks for your proof-reading. - (or ASan for short) That came a little late in the article because ASan already appeared in the introduction. - peak your interest -> pique your interest - Cppcon -> CppCon - an ulong -> a ulong (That's assuming

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Ali Çehreli via Digitalmars-d-announce
On 12/25/2017 03:17 PM, Johan Engelen wrote: >> 1. The gray-on-white text is not very legible. > > Looks great here, I like it, sorry. (made it completely black now, can't > see the difference here though) Yes, browsers report it to be black but it looks very gray :) on Linux Mint with both Fir

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Johan Engelen via Digitalmars-d-announce
On Monday, 25 December 2017 at 20:31:18 UTC, Walter Bright wrote: Thanks for the great article! Some suggestions: Thanks for your comments, I've incorporated them (to my liking). 1. The gray-on-white text is not very legible. Looks great here, I like it, sorry. (made it completely black n

Re: Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Walter Bright via Digitalmars-d-announce
On 12/25/2017 9:03 AM, Johan Engelen wrote: I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html "LDC comes with improved support for Address Sanitizer since the 1.4.0 release. Address

Article: Finding memory bugs in D code with AddressSanitizer

2017-12-25 Thread Johan Engelen via Digitalmars-d-announce
I've been writing this article since August, and finally found some time to finish it: http://johanengelen.github.io/ldc/2017/12/25/LDC-and-AddressSanitizer.html "LDC comes with improved support for Address Sanitizer since the 1.4.0 release. Address Sanitizer (ASan) is a runtime memory write/