Closed Bug 417560 Opened 17 years ago Closed 11 months ago

protect against Obj-C exceptions in "gfx" top-level directory

Categories

(Core Graveyard :: GFX, defect, P2)

x86
macOS
defect

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: jaas, Unassigned)

References

()

Details

Attachments

(2 files)

For implementing the strategy we decided on in bug 163260 we are filing a bug for each top-level directory that needs work. mozilla/gfx
Flags: blocking1.9+
What's the right solution for gfxQuartzFontCache.mm? Stan noted that it's compiled with exceptions disabled (bug 163260 comment 116).
#undef'ing try and catch at the top of the file is a hack, but on the plus side, it will give future generations a good laugh. You could try to suppress the -fno-exceptions to the file, that seems like more trouble than it's worth.
-fno-exceptions is defined for a lot of stuff, including all of cocoa widgets. Do we really care about it? Does it interfere with the obj-c exception stuff?
QA Contact: dmose → nobody
Flags: tracking1.9+ → blocking1.9+
We can't compile in gfx with obj-c exception handlers. This patch implements exception wrapping in one place to demonstrate the compile failure.
This is the output for the failure.
Security concerns over this don't warrant blocking 1.9, but will take a patch at any time.
Flags: wanted1.9.0.x+
Flags: blocking1.9-
Flags: blocking1.9+
Hey Josh. This is still blocking bug 163260. Have you been able to make any progress?
Also, what about 1.9.0.x vs 1.9.1?
Flags: wanted1.9.1?
Flags: wanted1.9.1? → wanted1.9.1+
Product: Core → Core Graveyard
Assignee: joshmoz → nobody
Is this bug really dead, or should it live in Gfx:Thebes instead of Core Graveyard?
Status: NEW → RESOLVED
Closed: 11 months ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: