Closed
Bug 496148
Opened 15 years ago
Closed 14 years ago
Remove SAFESEH from Win build settings
Categories
(Tamarin Graveyard :: Virtual Machine, defect, P4)
Tracking
(Not tracked)
RESOLVED
FIXED
Q3 11 - Serrano
People
(Reporter: rreitmai, Assigned: lhansen)
Details
(Whiteboard: Has patch)
Attachments
(1 file)
4.94 KB,
patch
|
rreitmai
:
review+
|
Details | Diff | Splinter Review |
This linker setting is probably no longer needed. It was there for the BufferGuard work (i.e exception handlers) which have already been removed.
Assignee | ||
Updated•15 years ago
|
Priority: -- → P3
Target Milestone: --- → flash10.1
Assignee | ||
Updated•15 years ago
|
Priority: P3 → P4
Assignee | ||
Comment 1•14 years ago
|
||
Rick: In the shell project we add /SAFESEH:NO and it's used nowhere else. Do you think we should remove that switch? http://msdn.microsoft.com/en-us/library/9a89h429%28VS.80%29.aspx
Reporter | ||
Comment 2•14 years ago
|
||
Yes, we only had it there since we didn't register buffer guard as a exception handler to the OS. There is player code that does the registration properly and thus they're not using the switch. If we need to , we can do the same, but I don't think bufferGuard is even in our code anymore , if it is we should stamp it out.
Comment 3•14 years ago
|
||
BufferGuard is loooong gone.
Assignee | ||
Updated•14 years ago
|
Assignee: nobody → lhansen
Comment 4•14 years ago
|
||
Should this also be removed from the configure.py script? http://hg.mozilla.org/tamarin-redux/annotate/tip/configure.py#l168 lhansen@1176 168 OS_LDFLAGS += "-SAFESEH:NO -MAP "
Assignee | ||
Comment 6•14 years ago
|
||
Attachment #438138 -
Flags: review?(rreitmai)
Assignee | ||
Updated•14 years ago
|
Whiteboard: Has patch
Reporter | ||
Updated•14 years ago
|
Attachment #438138 -
Flags: review?(rreitmai) → review+
Assignee | ||
Comment 7•14 years ago
|
||
tamarin-redux changeset: 4383:afe3bfb0f08f
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Updated•13 years ago
|
Flags: flashplayer-bug-
You need to log in
before you can comment on or make changes to this bug.
Description
•