OSCommerce Product Manager

OSCommerce Product Manager for Windows
Tasklist

FS#82 - Crash reporting needed.

Attached to Project: OSCommerce Product Manager
Opened by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 02:59 GMT-6
Last edited by Mario A. Valdez-Ramirez (mvaldez) - Sunday, 20 November 2005, 20:35 GMT-6
Task Type Bug Report
Category Backend / Core
Status Closed
Assigned To Mario A. Valdez-Ramirez (mvaldez)
Operating System All
Severity Low
Priority Urgent
Reported Version any
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Too many crashes reported already, most cannot be reproduced. A crash reporting function is needed.

We can try to develop our own or use an existing solution. All solutions are proprietary. On final review only two solutions were considered: MadExcept (http://www.madshi.net/olddlp3.htm) and EurekaLog (http://www.eurekalog.com/).

Both use proprietary licenses. However MadExcept is freeware for non-commercial use.

The big problem is that MadExcept is deeply linked to the OSCPMWin code. As we are releasing under GPL, we cannot distribute unless MadExcept become GPL too (Which won't happen anytime soon, as the wording of its license shows). We can include an exception in our GPL license, to allow linking with MadExcept (at least for the debug releases). As we are the full owners of the OSCPMWin application that is not a problem, but it is not clear if we need permission from indirect copyright holders (of the components code [zeoslib, indy, dxgettext, freeimage]).

This is really messy. If this cannot be clarified, we will be forced to write our own crash reporter.
This task depends upon

Closed by  Mario A. Valdez-Ramirez (mvaldez)
Sunday, 20 November 2005, 20:35 GMT-6
Reason for closing:  
Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 03:38 GMT-6

Pending to check all components licenses. Most have dual licenses or relaxed ones (BSD/MIT/etc).

Maybe we can actually make a debug release under a modified (non-open-source) license for the only purpose to link with MadExcept.

This sucks.


Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 06:31 GMT-6

FreeImage:
Dual-licensed under GPL and FreeImage Public License.
FreeImage Public License will allow us to build the debug version.

INDY Internet Direct:
Dual-licensed under modified-BSD and MPL.
Both allow us to build the debug version.

Zeos Library:
Licensed under LGPL.
LGPL will allow us to build the debug version.

PuTTY project:
Licensed under a MIT license.
MIT license will allow us to build the debug version.

GNU gettext for Delphi:
Licensed under a MIT license.
MIT license will allow us to build the debug version.

Images:
Dual-licensed under GPL and LGPL.
LGPL will allow us to build the debug version.


I think we can build it then. But it won't be under a GPL+exception, but under a freeware or something license.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Tuesday, 24 August 2004, 06:32 GMT-6

Usage of the software under a different license maybe helpful, but should be discouraged.

A big fat note saying DEBUG VERSION or something else, and a note in the download page about not using it unless completelly necessary.

Comment by Mario A. Valdez-Ramirez (mvaldez) - Wednesday, 22 September 2004, 16:26 GMT-6

We tried MadExcept, but it couldn't catch the errors that are our real problem (GPFs in Windows 9x/Me).

We are ending the active support for MadExcept from now on. We are leaving the conditionals in the code for a while.

Comment by Mario A. Valdez-Ramirez (mvaldez) - Wednesday, 22 September 2004, 16:27 GMT-6


This is closed as "Won't implement".
Comment by Mario A. Valdez-Ramirez (mvaldez) - Thursday, 07 April 2005, 06:55 GMT-6

This bug has been reopened. It is related to the Bug #170 (Licensing issue with included OSCommerce code).

As of today we are distributing a debug version (only-executable) under a freeware-like license. Our crashing report unit is the JclDebug unit from the JEDI project (which is released under MPL).

As long as we are the only lonely solo coder we are safe. Eventually we need to move to a GPL-compatible solution.
Comment by Mario A. Valdez-Ramirez (mvaldez) - Sunday, 20 November 2005, 20:35 GMT-6
After reviewing this problem and tested with a few cases of crashing, we have been able to discover the crashing reasons using just the MAP files. I think we can just rely on the manual MAP-file code-walktrhough method for now.

I am closing this bug now as "Will not fix".

Loading...