Opened 9 years ago

Closed 9 years ago

#763 closed defect (invalid)

FP exception handling and "random" FP exceptions

Reported by: gb Owned by:
Priority: normal Milestone: Future Clozure CL
Component: Foreign Function Interface Version: trunk
Keywords: Cc:

Description

On at least some fairly recent versions of OSX, using drag-and-drop to drag text around in the Cocoa IDE generates an FP exception (invalid operation IIRC). This happens deep in some CG text-drawing code that's invoked by CCL calling the superclass's #/mouseDown: method, and we report it as an arithmetic error. The error's likely to just be confusing and disruptive to the user.

We can work around this particular bug by disabling FP exceptions around the next-method call.

We generally try to report FP exceptions that occur in foreign code; this certainly makes sense if (for instance) #_sin is called as part of the implementation of CL:SIN. It's less clear that it's desirable or useful to try to detect and report FP exceptions that have nothing to do with CL math functions, though we've traditionally done so.

Change History (1)

comment:1 Changed 9 years ago by gb

  • Resolution set to invalid
  • Status changed from new to closed

I don't know why an FP exception was signaled here, but we generally only check for fp exceptions that may occur in foreign code when that foreign code is part of the implementation of a CL math function, and when we do this check we do it explicitly.

The underlying CG bug seems to have been fixed in OSX 10.6.5.

Note: See TracTickets for help on using tickets.