Re: [Bug-gnubg] Error Report

[Holger]

On Tue, 31 Dec 2002 09:43:04 +0100, Jacques Thiriat wrote:
> I downloaded the latest version, but unfortunately I can't start it.
> here are the details of the error message I get :
> 
> GNUBG a causé une défaillance de page dans
>  le module FREETYPE.DLL à 0167:65f20ce1.
> Registres :
> EAX=82922e64 CS=0167 EIP=65f20ce1 EFLGS=00010282
...
> I use the French version of Windows 98SE

On Tue, 31 Dec 2002 13:15:19 +0100, Lukas Rätz wrote:
> Unfortunately the new version of Gnubg crashes with an error
> referring to the module FREETYPE.DLL on my Windows 98 SE (German edition): 
> 
>   GNUBG verursachte einen Fehler durch eine ungültige Seite
>   in Modul FREETYPE.DLL bei 016f:65f20ce1.
>   Register:
>   EAX=826e4c00 CS=016f EIP=65f20ce1 EFLGS=00010286
...
> Closing all running programs (like virus shield etc.) and using older
> versions of freetype.dll did not work.
> There has not been any error with the older installation archive.

Hi, this type of error message is unfortunately completely useless and
typical for Microsoft. It's not even said that the freetype library
has caused this crash, it just happened there.

I've noticed this bug on my system (Win95), too, and have already
reported it to this mailing list on Dec 25 1:47 (Subject: [Bug-gnubg]
Obscure crash). (In case that you weren't aware that address@hidden
is a mailing list, you can access its archive under
http://mail.gnu.org/pipermail/bug-gnubg/ .)

I still couldn't debug this problem because I yet have to install
MinGW 2. But here is a little more information about it:

Good news first: (Here) It does _not_ occur on a freshly booted
system!

But after I've worked with a few different programmes usually
(always?) invoking GNUbg results in a crash right after the start.

In either way, when and after using the program or after a crash, my
system becomes instable. Even after closing GNUbg other programmes
crash out of the blue. Whether they were started before or after
invoking GNUbg doesn't matter.
This never [;-)] happens when I don't run GNUbg or with a version
prior to about Dec 4.

Regards and a Happy New Year,

        Holger