Closed
Bug 1245470
Opened 8 years ago
Closed 6 years ago
mingw-w64 compiled Firefox breaks with EMET (Tor 13893)
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
firefox47 | --- | affected |
People
(Reporter: gk, Assigned: gk)
References
(Blocks 1 open bug, )
Details
(Whiteboard: [tor][tor-standalone])
Compiling Firefox with mingw-w64 is broken if one is using Microsoft's EMET (https://support.microsoft.com/en-us/kb/2458544). EMET detects SimExecFlow mitigation and closes Firefox. This, however, does not happen if one is using --disable-optimize for compilation. It seems EMET does not like the optimized created by GCC. There is further information available starting with https://trac.torproject.org/projects/tor/ticket/13893#comment:16.
Assignee | ||
Comment 1•8 years ago
|
||
Might actually be as simple as doing the same as bug 1233208 for AvailableMemoryTracker, in case this is the right fix?
Flags: needinfo?(jacek)
Comment 2•8 years ago
|
||
I don't think that mingw is considered an important compiler target for the Mozilla project: we're focusing much of our Windows effort on clang-cl as a free alternative to MSVC. I'm happy to leave this bug open if you're planning on fixing it, otherwise I suggest we close INCOMPLETE.
Assignee | ||
Comment 3•8 years ago
|
||
(In reply to Benjamin Smedberg [:bsmedberg] from comment #2) > I don't think that mingw is considered an important compiler target for the > Mozilla project: we're focusing much of our Windows effort on clang-cl as a > free alternative to MSVC. I'm happy to leave this bug open if you're > planning on fixing it, otherwise I suggest we close INCOMPLETE. Yes, we plan to work on it.
Flags: needinfo?(jacek)
Updated•8 years ago
|
Priority: -- → P3
Updated•8 years ago
|
Summary: mingw-w64 compiled Firefox breaks with EMET → mingw-w64 compiled Firefox breaks with EMET (Tor 13893)
Updated•8 years ago
|
Whiteboard: [tor] → [tor][tor-standalone]
Assignee | ||
Updated•8 years ago
|
Assignee: nobody → gk
Updated•6 years ago
|
Flags: needinfo?(gk)
Assignee | ||
Comment 4•6 years ago
|
||
I think we can close the Mozilla side of this issue (i.e. this ticket). bug 1201205 helped a lot and the remaining things go away if one switches to GCC 6. So this is strictly speaking WORKSFORME from a Mozilla PoV.
Status: NEW → RESOLVED
Closed: 6 years ago
Flags: needinfo?(gk)
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•