Date:	Tue, 15 Jul 1997 13:00:17 +0300 (EET DST)
From:	Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Reply-To:	Esa DOT Peuha AT Helsinki DOT FI
To:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc:	Phil Galbiati <galbiati AT cse DOT ogi DOT edu>, djgpp AT delorie DOT com
Subject:	Re: Emacs 22 env vars bug
In-Reply-To:	<Pine.SUN.3.91.970713204509.28618L-100000@is>
Message-ID:	<Pine.SOL.3.96.970715124917.6183A-100000@kruuna.Helsinki.FI>
MIME-Version:	1.0

On Sun, 13 Jul 1997, Eli Zaretskii wrote:

> Yes, I also get the crash traceback which points into `gmalloc' (which
> is GNU's replacement for `malloc' and friends).  But I'm clueless as
> to why does it crash there, or why only for .exe built on my machine?

Here's the traceback again for reference (with line numbers from my
machine):

Call frame traceback EIPs:
  0x000761a6   __free_internal+1126, line 1105 of gmalloc.c
  0x0007642e   __realloc_internal+498, line 1379 of gmalloc.c
  0x0007646a   _realloc+50, line 1392 of gmalloc.c
  0x000491cb   _emacs_blocked_realloc+31, line 381 of alloc.c
  0x0007646a   _realloc+50, line 1392 of gmalloc.c
  0x000432d4   _regex_compile+2604, line 1957 of regex.c
  0x00048360   _re_compile_pattern+36, line 5177 of regex.c
  0x0003f495   _compile_pattern_1+81, line 126 of search.c
  0x0003f558   _compile_pattern+84, line 168 of search.c
  0x0003f898   _string_match_1+232, line 310 of search.c
  0x0003f927   _Fstring_match+19, line 336 of search.c

It's possible that `regex_compile' calls `realloc' with invalid pointer;
if so, the fault is an uninitialized pointer in `search.c'. I'll change
`_free_internal' to recognize this, and will post the patch for testing.

Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/

- Raw text -