[Xapian-tickets] [Xapian] #170: Windows structured exceptions produce RuntimeError with some MSVC versions

[Xapian]

#170: Windows structured exceptions produce RuntimeError with some MSVC versions
-------------------------------+--------------------------------------------
 Reporter:  sidnei             |        Owner:  olly     
     Type:  defect             |       Status:  closed   
 Priority:  normal             |    Milestone:           
Component:  Xapian-bindings    |      Version:  SVN trunk
 Severity:  normal             |   Resolution:  wontfix  
 Keywords:                     |    Blockedby:           
 Platform:  Microsoft Windows  |     Blocking:           
-------------------------------+--------------------------------------------
Changes (by olly):

  * status:  assigned => closed
  * resolution:  => wontfix


Old description:

> We are having an issue on a testing machine. We are running stress tests
> on it,
> and Xapian eventually raises a RuntimeError, "unknown Xapian error".
>
> This is on Windows, using the Xapian Python bindings.
>
> Richard mentioned that exception.i has a catch(...) that catches all the
> unknown
> exceptions.
>
> He also mentioned that this might have something to do with Windows
> Structured
> Exceptions, and that Mark had investigated this previously so he thought
> it had
> been fixed.

New description:

 We are having an issue on a testing machine. We are running stress tests
 on it,
 and Xapian eventually raises a RuntimeError, "unknown Xapian error".

 This is on Windows, using the Xapian Python bindings.

 Richard mentioned that exception.i has a catch(...) that catches all the
 unknown
 exceptions.

 He also mentioned that this might have something to do with Windows
 Structured
 Exceptions, and that Mark had investigated this previously so he thought
 it had
 been fixed.

--

Comment:

 MSVC 8.0 and newer don't catch SEH exceptions in {{{catch (...)}}}.  Since
 the key issue here was that Xapian catching SEH exceptions makes debugging
 them harder, this ticket is only relevant for compiler versions prior to
 MSVC 8.0, which was released in November 2005 (over 4 years ago).

 And it seems that Microsoft no longer support the C++ part of VS 2003,
 which was the version before 8.0:

 http://msdn.microsoft.com/en-us/vstudio/aa948854.aspx

 So it seems time has made this issue less relevant.  Our informal policy
 is that we don't go out of our way to support platforms and compilers
 which aren't supported "upstream", and since nobody is working on this
 issue, I'm closing it as "wontfix".

-- 
Ticket URL: <http://trac.xapian.org/ticket/170#comment:14>
Xapian <http://xapian.org/>
Xapian