🚀 go-pugleaf

hi

The contents of this message do not relate directly to emacs but I have been
unable to come up with an e-mail address for problems relating to the gnu
debugger (gdb).  I hope you might be kind enough to relay this message to
an appropriate address or provide me with an appropriate address.  

I am using gdb (version 3.5) on a Sun Sparc 1+ (with SunOs 4.1) as well as
gnu emacs (version 18.55).  The problem I have encountered relates to gdb's
handling of SIGINT.  Below I have included the status of the relevant stty
paramters as reported via the command "stty all":

********************

pygmy[/home/dswift]> stty all
speed 38400 baud, 24 rows, 80 columns; evenp
-inpck imaxbel
iexten crt
erase  kill   werase rprnt  flush  lnext  susp   intr   quit   stop   eof
^?     ^U     ^W     ^R     ^O     ^V     ^Z/^Y  ^C     ^\     ^S/^Q  ^D

********************

Note that the interrupt character is mapped to ^C.  Unfortunately, gdb
does not cause the program being debugged to stop running when I type 
control-C from the keyboard (note: gdb was launched from the unix cshell...
not from within emacs).  Moreover, the character ^Z causes gdb to be suspended
but not its daughter process.  When I use the gdb-mode within emacs, the
character sequence ^C^C should interrupt the program being debugged but has
no effect.  The sequence ^C^Z causes gdb to be killed.

To add to the confusion, I have gdb (version 3.2) and emacs (version 18.55)
running on a Sun 360 (SunOs 3.5) and the status of stty is given below:

********************

right[/usr/swift]> stty all
new tty, speed 38400 baud, 0 rows, 0 columns; tabs
crt
decctlq
erase  kill   werase rprnt  flush  lnext  susp   intr   quit   stop   eof
^?     ^U     ^W     ^R     ^O     ^V     ^Z/^Y  ^C     ^\     ^S/^Q  ^D

********************

On this machine, gdb handles interrupts and suspends as I would expect.  The
program being debugged is stopped and gdb's command line prompts for further
commands.  

Incidentally, I used the gdb command "info signal" to make sure that the
table entries for SIGINT were correct (as shown below):

Number  Stop    Print   Pass to program Description

0       Yes     Yes     Yes             Signal 0
1       Yes     Yes     Yes             Hangup
2       Yes     Yes     No              Interrupt
3       Yes     Yes     Yes             Quit
4       Yes     Yes     Yes             Illegal instruction

Perhaps you can suggest steps I can take to enable gdb to trap and 
respond correctly to interrupt signals.  I would be happy to have you
contact me if you need further information.


Thank you!

Dana Swift
School of Oceanography
University of Washington
(206) 543-6697
e-mail: swift@right.ocean.washington.edu