FROM : j o a r
DATE : Wed Apr 13 12:59:49 2005
File a bug report to Apple, and attach the offending EPS file.
You should of course not crash, regardless of what the file you try to
read contains.
j o a r
On 2005-04-13, at 11.30, Stefan Landvogt wrote:
> I try to load some EPS files and save them as JPG. That works fine for
> almost all of the files. Almost. One file is leading to the following
> exception.
>
> Exception: EXC_BAD_ACCESS (0x0001)
> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x002df000
>
> Thread 0 Crashed:
> 0 libSystem.B.dylib 0x90006e40 strlen + 0x20
> 1 libSystem.B.dylib 0x90016e68 sscanf + 0x68
> 2 com.apple.AppKit 0x9305ea68 -[NSEPSImageRep(Private)
> _readBBox] + 0xd0
> 3 com.apple.AppKit 0x9305e7a8 -[NSEPSImageRep
> initWithData:] + 0x78
> 4 com.apple.AppKit 0x9305e1c4 +[NSEPSImageRep
> imageRepWithData:] + 0x38
>
> The same problem happens, when I drag&drop the file into Mail: Mail
> crashes.
> The Preview-Application can open the file just fine (it converts it
> somehow in PDF in displays it), so they go a different route than
> NSEPSImageRep.
>
> I tried to put an exception handler around the calling code:
>
> NS_DURING
> returnImageRep = [NSEPSImageRep imageRepWithData: currentData];
> NS_HANDLER
> returnImageRep = nil;
> NSLog(@"SOMETHING BAD HAPPENED");
> NS_ENDHANDLER
>
> but that did not help either.
>
> My question: Is there something I can do to work around? It would be
> great e.g. to copy that "bad" file into a qurantaine-folder and
> writing a log message.
DATE : Wed Apr 13 12:59:49 2005
File a bug report to Apple, and attach the offending EPS file.
You should of course not crash, regardless of what the file you try to
read contains.
j o a r
On 2005-04-13, at 11.30, Stefan Landvogt wrote:
> I try to load some EPS files and save them as JPG. That works fine for
> almost all of the files. Almost. One file is leading to the following
> exception.
>
> Exception: EXC_BAD_ACCESS (0x0001)
> Codes: KERN_INVALID_ADDRESS (0x0001) at 0x002df000
>
> Thread 0 Crashed:
> 0 libSystem.B.dylib 0x90006e40 strlen + 0x20
> 1 libSystem.B.dylib 0x90016e68 sscanf + 0x68
> 2 com.apple.AppKit 0x9305ea68 -[NSEPSImageRep(Private)
> _readBBox] + 0xd0
> 3 com.apple.AppKit 0x9305e7a8 -[NSEPSImageRep
> initWithData:] + 0x78
> 4 com.apple.AppKit 0x9305e1c4 +[NSEPSImageRep
> imageRepWithData:] + 0x38
>
> The same problem happens, when I drag&drop the file into Mail: Mail
> crashes.
> The Preview-Application can open the file just fine (it converts it
> somehow in PDF in displays it), so they go a different route than
> NSEPSImageRep.
>
> I tried to put an exception handler around the calling code:
>
> NS_DURING
> returnImageRep = [NSEPSImageRep imageRepWithData: currentData];
> NS_HANDLER
> returnImageRep = nil;
> NSLog(@"SOMETHING BAD HAPPENED");
> NS_ENDHANDLER
>
> but that did not help either.
>
> My question: Is there something I can do to work around? It would be
> great e.g. to copy that "bad" file into a qurantaine-folder and
> writing a log message.
| Related mails | Author | Date |
|---|---|---|
| Stefan Landvogt | Apr 13, 11:30 | |
| j o a r | Apr 13, 12:59 |






Cocoa mail archive

