It's amazing and quite hard for me to understand. WebKit library on Windows has been around for a while. The file that I cited is used for everywhere. AFAIK, Google Chromes and Safari on Windows are built on top of WebKit. How come such a basic issue is showing up now?

I am using a pre-built WebKit library directly and I cannot and I am not in a position to change the code.

The code in JPEGImageDecoder.cpp says, if there is a catastropic error, longjmp would be called. setjmp is just for preparing for that. Now I am crashing at setjmp, which happens before any error event.

Any thoughts how to handle this issue?


On Mon, Apr 26, 2010 at 12:27 PM, Greg Chicares <> wrote:
On 2010-04-26 19:02Z, SCU Rock wrote:
> On Mon, Apr 26, 2010 at 2:00 AM, Tor Lillqvist <> wrote:
>>> What can be the cause of the crash?
>> Most likely, a bug in your code.
> While it is still possible that this is a bug in my code, it is not
> likely. The crash point is from a stable library WebKit, file
> JPEGImageDecoder.cpp, line #169(
> 169           if  (setjmp(m_err.setjmp_buffer)) {
| Do not use setjmp  and longjmp  in C++ programs

Line 63 of the file you cited says:
 jmp_buf setjmp_buffer;     // For handling catastropic errors
You might want to consider changing the code, either to use
C++ exceptions, or simply to call terminate().

MinGW-users mailing list

This list observes the Etiquette found at
We ask that you be polite and do the same.  Disregard for the list etiquette may cause your account to be moderated.

You may change your MinGW Account Options or unsubscribe at: