← Back to index | Original Bugzilla link

Bug 10050 – Regression (git-head): RDMD no longer emits error messages from DMD

Status
RESOLVED
Resolution
FIXED
Severity
regression
Priority
P2
Component
dmd
Product
D
Version
D2
Platform
All
OS
All
Creation time
2013-05-09T11:23:00Z
Last change time
2013-05-10T02:36:48Z
Keywords
pull
Assigned to
nobody
Creator
andrej.mitrovich

Comments

Comment #0 by andrej.mitrovich — 2013-05-09T11:23:29Z
test.d: ---- void main() { foobar; } ---- 2.062: $ rdmd --force test.d > test.d(3): Error: undefined identifier foobar > Failed: "dmd" "-v" "-o-" "test.d" "-I." git-head: $ rdmd --force test.d > Failed: ^"dmd^" ^"-v^" ^"-o-^" ^"test.d^" ^"-I.^" Tested on Win7 x64.
Comment #1 by andrej.mitrovich — 2013-05-09T11:29:07Z
I can also recreate this with the RDMD binary from 2.062, so something about DMD had to have changed. Has it recently switched emitting errors from stdout to stderr or vice-versa? That could explain int.
Comment #2 by andrej.mitrovich — 2013-05-09T11:29:19Z
(In reply to comment #1) > That could explain int. s/int/it.
Comment #3 by k.hara.pg — 2013-05-10T00:06:37Z
(In reply to comment #1) > I can also recreate this with the RDMD binary from 2.062, so something about > DMD had to have changed. Has it recently switched emitting errors from stdout > to stderr or vice-versa? That could explain it. This is changed with: https://github.com/D-Programming-Language/dmd/pull/1959
Comment #4 by yebblies — 2013-05-10T00:22:03Z
https://github.com/D-Programming-Language/dmd/pull/2001
Comment #5 by github-bugzilla — 2013-05-10T00:52:26Z
Commits pushed to master at https://github.com/D-Programming-Language/dmd https://github.com/D-Programming-Language/dmd/commit/2f19459aba138966b5c66fb242259505fa29f740 Fix Issue 10050 - Replace stdmsg with stderr https://github.com/D-Programming-Language/dmd/commit/72014d3476c69d148d720a7fbb701ceda60a453c Merge pull request #2001 from yebblies/stdmsgerr [REG2.063a] Issue 10050 - Replace stdmsg with stderr
Comment #6 by andrej.mitrovich — 2013-05-10T02:36:48Z
Thanks, I can confirm it's fixed now.