Seqfault doing kill -l
Hi, Couldn't find a mention of this in the Cygwin mailing list archives and thought I'd ask about it. I was trying to get the list of siginals that cygwins kill (/bin/kill) takes using the kill -l command (and --list). Unfortuantly it causes it to segfault as you can see from the following output, thought the other kill in /usr/bin/kill works okay. Is this a known issue? [EMAIL PROTECTED] ~ $ /bin/kill --list Segmentation fault (core dumped) [EMAIL PROTECTED] ~ $ /bin/kill --version kill (cygwin) 1.14 Process Signaller Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002 Red Hat, Inc. Compiled on Mar 18 2004 I have captured a stack trace [EMAIL PROTECTED] ~ $ gdb /bin/kill GNU gdb 2003-09-20-cvs (cygwin-special) Copyright 2003 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 i686-pc-cygwin...(no debugging symbols found)... (gdb) run -l Starting program: /usr/bin/kill.exe -l Program received signal SIGSEGV, Segmentation fault. 0x610cdb11 in strlen () from /usr/bin/cygwin1.dll (gdb) bt #0 0x610cdb11 in strlen () from /usr/bin/cygwin1.dll #1 0x610d18fc in wmemset () from /usr/bin/cygwin1.dll #2 0x610d1014 in wmemset () from /usr/bin/cygwin1.dll #3 0x610de407 in wmemset () from /usr/bin/cygwin1.dll #4 0x610882af in cygwin1!aclcheck () from /usr/bin/cygwin1.dll #5 0x00401b5f in ?? () (gdb) [EMAIL PROTECTED] ~ $ which kill /usr/bin/kill [EMAIL PROTECTED] ~ $ 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) SIGURG 17) SIGSTOP 18) SIGTSTP 19) SIGCONT 20) SIGCHLD 21) SIGTTIN 22) SIGTTOU 23) SIGIO 24) SIGXCPU 25) SIGXFSZ 26) SIGVTALRM 27) SIGPROF 28) SIGWINCH 29) SIGLOST 30) SIGUSR1 31) SIGUSR2 [EMAIL PROTECTED] ~ $ kill -v bash: kill: v: invalid signal specification Rob -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Seqfault doing kill -l
On Thu, 27 May 2004, Robert McGovern wrote: Hi, Couldn't find a mention of this in the Cygwin mailing list archives and thought I'd ask about it. I was trying to get the list of siginals that cygwins kill (/bin/kill) takes using the kill -l command (and --list). Unfortuantly it causes it to segfault as you can see from the following output, thought the other kill in /usr/bin/kill works okay. Is this a known issue? Confirmed. This just got fixed in CVS by Christopher Faylor, BTW: http://cygwin.com/ml/cygwin-cvs/2004-q2/msg00210.html. [EMAIL PROTECTED] ~ $ /bin/kill --list Segmentation fault (core dumped) [EMAIL PROTECTED] ~ $ /bin/kill --version kill (cygwin) 1.14 Process Signaller Copyright 1996, 1997, 1998, 1999, 2000, 2001, 2002 Red Hat, Inc. Compiled on Mar 18 2004 I have captured a stack trace [snip] FYI, the stack trace is worthless, as it's on an optimized non-debug version of cygwin1.dll. [EMAIL PROTECTED] ~ $ which kill /usr/bin/kill You should have used type kill, which would have shown you that kill is a shell builtin. HTH, Igor -- http://cs.nyu.edu/~pechtcha/ |\ _,,,---,,_[EMAIL PROTECTED] ZZZzz /,`.-'`'-. ;-;;,_[EMAIL PROTECTED] |,4- ) )-,_. ,\ ( `'-' Igor Pechtchanski, Ph.D. '---''(_/--' `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-. Meow! I have since come to realize that being between your mentor and his route to the bathroom is a major career booster. -- Patrick Naughton -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Seqfault doing kill -l
On Thu, May 27, 2004 at 04:02:21PM +0100, Robert McGovern wrote: [EMAIL PROTECTED] ~ $ /bin/kill --list Segmentation fault (core dumped) This should be fixed in the current snapshot. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
Re: Seqfault doing kill -l
Thanks for that Igor Christopher, Regarding using type rather than which. I actually hadn't realised there was a command called type in the shell. I obviously haven't used bash enough. Rob (apologies for top posting, I use Novell GroupWise and it only does replies this way) [EMAIL PROTECTED] 05/27/04 04:36pm On Thu, 27 May 2004, Robert McGovern wrote: Hi, Couldn't find a mention of this in the Cygwin mailing list archives and thought I'd ask about it. I was trying to get the list of siginals that cygwins kill (/bin/kill) takes using the kill -l command (and --list). Unfortuantly it causes it to segfault as you can see from the following output, thought the other kill in /usr/bin/kill works okay. Is this a known issue? Confirmed. This just got fixed in CVS by Christopher Faylor, BTW: http://cygwin.com/ml/cygwin-cvs/2004-q2/msg00210.html. snip -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
RE: Seqfault doing kill -l
-Original Message- From: cygwin-owner On Behalf Of Robert McGovern Sent: 27 May 2004 16:54 Thanks for that Igor Christopher, Regarding using type rather than which. I actually hadn't realised there was a command called type in the shell. I obviously haven't used bash enough. Rob (apologies for top posting, I use Novell GroupWise and it only does replies this way) Are you really claiming that it won't let you move the cursor to after the quoted text and type new text? Nor would it let you copy and paste the quoted text from the top of the message to the bottom? Yet it does let you edit the quoted text enough to delete some and replace it with the word snip, as you did in that post? That seems rather strange to me. [EMAIL PROTECTED] THAT'S BAD!] Please, please, read http://cygwin.com/acronyms/#PCYMTNQREAIYR cheers, DaveK -- Can't think of a witty .sigline today -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
