Path: utzoo!telly!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!iuvax!cica!tut.cis.ohio-state.edu!ai.mit.edu!frame!viking!dpb
From: frame!viking!dpb@ai.mit.edu (Don Bennett           433-3311, 408)
Newsgroups: gnu.gdb.bug
Subject: alloca failure in symbol table read
Message-ID: <8907172332.AA03822@viking.>
Date: 17 Jul 89 23:32:48 GMT
Sender: daemon@tut.cis.ohio-state.edu
Reply-To: dpb@frame.com
Distribution: gnu
Organization: GNUs Not Usenet
Lines: 22


gdb version: 3.2
machine type: sun-3/80
OS version: sun-os 4.0.3

Under both cc and gcc-1.35, the alloca that attempted to allocate
the buffer for the string table failed, returning a bad non-NULL
pointer (I only checked the return value on the gcc compiled version).

I worked around the problem by #define-ing BROKEN_LARGE_ALLOCA
when compiling this file.

My string table size was 5108024.

What determines the maximum allowable alloca size?

Thanks for releasing the new version, I've been wanting 
command-line/history editing ever since I heard it was in the works.

   Don Bennett           (408)433-3311
   dpb@frame.com
   Frame Technology