Message-Id: <3.0.1.32.20010402073555.006c5e2c@wingate>
X-Sender: n_abing#ns DOT roxas-online DOT net DOT ph AT wingate
X-Mailer: Windows Eudora Pro Version 3.0.1 (32)
Date: Mon, 02 Apr 2001 07:35:55 +0800
To: eliz AT is DOT elta DOT co DOT il
From: "Nimrod A. Abing" <n_abing AT ns DOT roxas-online DOT net DOT ph>
Subject: That crash message from the core dumper.
Cc: djgpp-workers AT delorie DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Reply-To: djgpp-workers AT delorie DOT com

Hello.

Here's the crash message that I was talking about, it's been symify'ed for
your convenience.

[---cut here---]
Abort!
Exiting due to signal SIGABRT
Raised at eip=00003786
writing contents of address 00237000
block size 524288

writing contents of address 00020000
block size 2228224
Exiting due to signal SIGSEGV
An error occured while writing core file. (signal: 14, progress number: 11)
Page fault at eip=000090b1, error=0004
eax=00000200 ebx=00004000 ecx=00001000 edx=00013d00 esi=00030000 edi=00013d00
ebp=002b6d2c esp=002b6d1c program=C:\PROJECTS\PMDB\COREDUMP\ABRT.EXE
cs: sel=021f  base=830fd000  limit=002b6fff
ds: sel=0247  base=830fd000  limit=002b6fff
es: sel=0257  base=00000000  limit=0010ffff
fs: sel=0257  base=00000000  limit=0010ffff
gs: sel=0257  base=00000000  limit=0010ffff
ss: sel=0247  base=830fd000  limit=002b6fff
App stack: [002b7000..00237000]  Exceptn stack: [0000ff30..0000dff0]

Call frame traceback EIPs:
  0x000090b1 ___dj_movedata+33
  0x000087dc ___dosmemput+44
  0x0000572b __write+123
  0x00002d85 __crt0_init_mcount+6089
  0x000036e5 ___djgpp_traceback_exit+177
  0x00003786 _raise+118
  0x00006094 _abort+36
  0x00003e6b _f1+11
  0x00003e7f _f2+11
  0x00003e8f _f3+11
  0x00003e9f _main+11
  0x000052d8 ___crt1_startup+204

[---cut here---]

and here's the program that I ran to test the core dumper:

[---cut here---]
#include <stdlib.h>
#include <coredump.h>
#include <signal.h>



void f1 ()
{
	abort ();
}

void f2 ()
{
	f1 ();
}

void f3 ()
{
	f2 ();
}

int main (int argc, char **argv)
{
	f3 ();
	exit (0);
}
[---cut here---]

Anyway, I've tracked it down to my AV software as I've mentioned in a
previous post. I turned off real-time scanning and everything went on
smoothly.


nimrod_a_abing
--------------

+========================================+
|  Home page: www.geocities.com/n_abing  |
+========================================+

"Tinimbang ka ngunit kulang."
If you understand that phrase, i-email mo'ko. ;-)