Message-ID: <000a01be47cd$41cd6480$5028bcca@harveen.tm.net.my>
From: "Guan Foo Wah" <jgfw AT usa DOT net>
To: <allegro AT canvaslink DOT com>
Cc: <djgpp AT delorie DOT com>
Subject: Attention JGMOD users with DJGPP 2.02
Date: Mon, 25 Jan 1999 03:10:25 +0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Reply-To: djgpp AT delorie DOT com

I just found a problem when JGMOD is running on DJGPP 2.02.

JGMOD couln't load certain S3M files (crashes when load_mod() is called
after allegro_init() function) when "Allegro.cfg" created by setup.exe
exists. MOD and XM seems to be OK so far. JGM is untested but should be OK,
I think. Unreal UMX is unrested also and I think it will have some problem
just like S3M.



I am still searching for the reasons this bug. There are 3 solutions that
I can think of currently to avoid this problem :-

1. Use DJGPP 2.01 instead of DJGPP 2.02
2. Or delete "Allegro.cfg"
3. Or call load_mod() before calling allegro_init()




Here is the output when I symified JGMOD.EXE which is compiled with
debugging info for JGMOD (not allegro). I am currently using Allegro 3.1
(official version)

Shutting down Allegro
Exiting due to signal SIGSEGV
General Protection Fault at eip=000135d1
eax=4527ff00 ebx=00000002 ecx=00000000 edx=000041bc esi=00000000
edi=00000ff5
ebp=00000007 esp=0010b24c program=D:\PROGM\JGMOD\SRC\JGMOD.EXE
cs: sel=00af  base=82604000  limit=0011ffff
ds: sel=00b7  base=82604000  limit=0011ffff
es: sel=00b7  base=82604000  limit=0011ffff
fs: sel=00c7  base=00000000  limit=0010ffff
gs: sel=00c7  base=00000000  limit=0010ffff
ss: sel=00b7  base=82604000  limit=0011ffff
App stack: [0010b3c8..0008b3c8]  Exceptn stack: [0008b2a8..00089368]

Call frame traceback EIPs:
  0x000135d1   _pack_mputl+1745

When loading S3M files or other module types, JGMOD doesn't write anything
to any files. It just read and that all. JGMOD doesn't use pack_mputl() at
all, but pack_iputl() in file save_jgm.c only. So it is funny and puzzling
to see that _pack_mputl() is reported.

To experience programers, can you figure or guess what is happening based on
the symified report above ?? Is DJGPP 2.02 known to be buggy ??