From: DEW16@daimlerchrysler.com
To: zsh-workers@sunsite.auc.dk
Subject: Signal-handling problem
Date: Tue, 9 Mar 1999 15:50:00 -0500 [thread overview]
Message-ID: <8525672F.0072267A.00@lngodd02.notes.chrysler.com> (raw)
Hello, all. Okay, so I *LOVE* zsh, but I have a small problem. For some
reason, my build doesn't know how to handle signals. For example, if I type:
dave(4):[~]% echo $ZSH_VERSION
3.0.5
dave(4):[~]% kill -l
ZERR
it only shows "ZERR". If I do the same thing in bash, I get:
dave(173):[~]% kill -l
1) SIGHUP 2) SIGINT 3) SIGQUIT 4) SIGILL
5) SIGTRAP 6) SIGABRT 7) SIGEMT 8) SIGFPE
9) SIGKILL 10) SIGBUS 11) SIGSEGV 12) SIGSYS
13) SIGPIPE 14) SIGALRM 15) SIGTERM 16) SIGUSR1
17) SIGUSR2 18) SIGCHLD 19) SIGPWR 20) SIGWINCH
21) SIGURG 22) SIGIO 23) SIGSTOP 24) SIGTSTP
25) SIGCONT 26) SIGTTIN 27) SIGTTOU 28) SIGVTALRM
29) SIGPROF 30) SIGXCPU 31) SIGXFSZ
All signals seem to kill my zsh and dump a core. Here's some gdb output from
one of them (caused by trying to suspend a job with CTRL-Z):
dave(3):[~]% gdb zsh core
GNU gdb 4.17
Copyright 1998 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "mips-sgi-irix6.4"...
Core was generated by `zsh'.
Program terminated with signal 10, Bus error.
Reading symbols from /usr/lib32/libcurses.so...done.
Reading symbols from /usr/lib32/libc.so.1...done.
#0 0x10057390 in dupstruct ()
(gdb) backtrace
#0 0x10057390 in dupstruct ()
#1 0x1004be04 in dotrapargs ()
#2 0x1004bf3c in dotrap ()
#3 0x1004b680 in handler ()
#4 <signal handler called>
#5 0xfa3cab8 in ksigprocmask () at crypt.c:105
(gdb)
Any ideas how I can fix this? (I compiled 'out-of-the-box', with no changes to
the configure script.) I really hope it's possible, because I *really* like
this shell! My platform is an SGI Onyx2 running IRIX 6.4...
TIA,
Dave Wolfe
gForce Techologies
c/o DaimlerChrysler
next reply other threads:[~1999-03-09 20:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-03-09 20:50 DEW16 [this message]
-- strict thread matches above, loose matches on Subject: below --
1999-03-10 23:43 DEW16
1999-03-09 19:17 DEW16
1999-03-10 8:53 ` Peter Stephenson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8525672F.0072267A.00@lngodd02.notes.chrysler.com \
--to=dew16@daimlerchrysler.com \
--cc=zsh-workers@sunsite.auc.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).