Open
Bug 1517076
Opened 7 years ago
Updated 3 years ago
On Windows, Some Rust allocation stacks in DMD bail out before reaching anything useful
Categories
(Core :: XPCOM, defect)
Core
XPCOM
Tracking
()
NEW
People
(Reporter: bholley, Unassigned)
Details
Attachments
(1 file)
|
7.73 KB,
text/plain
|
Details |
STR:
(1) Do an --enable-optimize --enable-dmd build on windows
(2) enable WR if the hardware isn't pre-qualified
(3) save the DMD report
(4) process it
I get something like the attached log. The top two items don't have usable stacks.
I'm going to try with an unoptimized build to see if things are better.
| Reporter | ||
Comment 1•7 years ago
|
||
(In reply to Bobby Holley (:bholley) from comment #0)
> I'm going to try with an unoptimized build to see if things are better.
(Though actually this build was also --enable-debug-rust, so I doubt it'll help).
Comment 2•7 years ago
|
||
This is probably going to be an issue with whatever XPCOM stackwalker that DMD uses rather than something in DMD per se. 4MB of mystery stacks doesn't sound too bad in the grand scheme of things.
Component: DMD → XPCOM
Updated•3 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•