gdb 4.6 interrupt problem?

Article View: gnu.gdb.bug

Article #428

#428

From: David Favor
Date: Wed, 09 Sep 1992 14:56

12 lines
1044 bytes

I'm using gdb-4.6 (with no patches applied) under SunOS 4.1.2
for the first time (this off course may be the problem). when
I continue (cont) a program under gdb control then type ^C control
is never returned to gdb. 'info signal 2' says...

(gdb) info signal 2
Signal          Stop    Print   Pass to program Description
SIGINT (2)      Yes     Yes     No              Interrupt

pressing ^C displays '^C', however, gdb continues instead of
returning control to the command line. what am I missing here?
how can I ^C during program execution to interact with gdb?

Technical Details

Message-ID: <3938@tivoli.UUCP>

Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!logan.tivoli.com!dfavor

Show Full Headers

Complete Article Headers

Newsgroups: gnu.gdb.bug
Path: arc1-ca.pugleaf.net!sparky!uunet!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!cis.ohio-state.edu!logan.tivoli.com!dfavor
From: dfavor@logan.tivoli.com (David Favor)
Subject: gdb 4.6 interrupt problem?
Message-ID: <3938@tivoli.UUCP>
Keywords: gdb,interrupt,problem,signal,gnu,debugger
Sender: gnulists@ai.mit.edu
Organization: TIVOLI Systems, Inc.
Distribution: gnu
Date: Wed, 9 Sep 1992 14:56:01 GMT
Approved: bug-gdb@prep.ai.mit.edu
Lines: 13