Article View: gnu.gdb.bug
Article #9938string constants
From: Richard A. Lethin
Date: Wed, 28 Nov 1990 01:04
Date: Wed, 28 Nov 1990 01:04
21 lines
1048 bytes
1048 bytes
If one tries to construct a command-line string constant, gdb dies. Program received signal 2, Interrupt #0 0x95cdc in read () (gdb) print "a" Inferior Gdb segmentation fault At first glance, this looks hard, but at second glance, it should be relatively easy to allocate space for the string on the stack. On third glance... This is for version GDB 3.5.1, Copyright (C) 1989 Free Software Foundation, Inc. running on a Sun 4/65
Technical Details
Message-ID:
<9011280104.AA01644@porridge>Path:
arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!AI.MIT.EDU!lethinShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: f5053,9670bf7bcb4cc106,start X-Google-Attributes: gidf5053,public X-Google-ArrivalTime: 1990-11-27 17:04:34 PST Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!tut.cis.ohio-state.edu!AI.MIT.EDU!lethin From: lethin@AI.MIT.EDU (Richard A. Lethin) Newsgroups: gnu.gdb.bug Subject: string constants Message-ID: <9011280104.AA01644@porridge> Date: 28 Nov 90 01:04:34 GMT Sender: daemon@tut.cis.ohio-state.edu Distribution: gnu Organization: GNUs Not Usenet Lines: 21 Approved: bug-gdb@prep.ai.mit.edu Posted: Wed Nov 28 02:04:34 1990