From: k3040e4 AT c210 DOT edvz DOT uni-linz DOT ac DOT at (Oberhumer Markus)
Message-Id: <199608301159.NAA15260@c210.edvz.uni-linz.ac.at>
Subject: response file problems
To: djgpp-workers AT delorie DOT com (djgpp-workers)
Date: Fri, 30 Aug 1996 13:59:14 -0200 (MET DST)
Return-Read-To: markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at
Content-Type: text
Content-Length: 1170      


===============================================================================
Markus F.X.J. Oberhumer <markus DOT oberhumer AT jk DOT uni-linz DOT ac DOT at>

Subject: response file problems
To: djgpp-workers AT delorie DOT com
===============================================================================

Recently I've done some torture-tests of my LZO libary and
run the test program on a complete patition of my hard dist.

I typed the following:
  gnufind / -type f > files.lst    (producing a 380 kB file)
  lzo_test @files.lst > log.txt

Problem 1:
  Crash in the startup code. I tracked this down to
  expand_response_files() in c1args.c which uses alloca
  when reading the file. Probably should use malloc()/free()
  if stackavail() < size_of_file - 16384 or something.
  Stubediting (increasing the stack size) is a temporary
  solution.

Problem 2:
  It looks like a filename "x'c" is perfectly valid under DOS.
  The parsing of the response file was completly confused
  by this. I don't know an easy solution but I think that
  EMX handles this problem by storing some flags in argv[x][-1]
  which indicate where the argument came from and how it should
  be expanded/quoted.