Re: Bash 3.0-2 and kill

2005-07-01 Thread Eric Blake
Eric Blake byu.net> writes: > > I have gotten to the point where I am seeing reproducible crashes in a > plain debugging version of bash inside gdb, but that the problem appears > to be malloc'd memory corruption (I hate those bugs - they are so hard to > pinpoint). I now have to attempt to buil

Re: Bash 3.0-2 and kill

2005-06-27 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Angelo Graziosi on 6/24/2005 3:26 PM: > I have noted that when one uses > >kill -9 > > in bash 3.0-2 (test), the command kills the process but also bash (even > if one uses /bin/kill...). > I have gotten to the point where I am s

Re: Bash 3.0-2 and kill

2005-06-25 Thread Igor Pechtchanski
Ugh. Top posting. Reformatted. On Sun, 26 Jun 2005, Angelo Graziosi wrote: > On Fri, 24 Jun 2005, Igor Pechtchanski wrote: > > > On Fri, 24 Jun 2005, Angelo Graziosi wrote: > > > > > I have noted that when one uses > > > > > >kill -9 > > > > > > in bash 3.0-2 (test), the command kills the

Re: Bash 3.0-2 and kill

2005-06-25 Thread Angelo Graziosi
Suppose that the command "ps" shows that an application, has a PID 1234 then kill -9 1234 kills the application but also the bash (3.0-2), i.e. closes the windows in which bash is running (for example the dos box or xterm). In some cases, in $HOME there is bash.exe.stackdump. After these t

Re: Bash 3.0-2 and kill

2005-06-25 Thread Christopher Faylor
On Sat, Jun 25, 2005 at 11:22:04AM -0400, Christopher Faylor wrote: >On Sat, Jun 25, 2005 at 09:05:12AM -0600, Eric Blake wrote: >>According to Igor Pechtchanski on 6/24/2005 10:50 PM: Given that if cygwin was this broken all sorts of other things would be broken as well, this is more likel

Re: Bash 3.0-2 and kill

2005-06-25 Thread Christopher Faylor
On Sat, Jun 25, 2005 at 09:05:12AM -0600, Eric Blake wrote: >According to Igor Pechtchanski on 6/24/2005 10:50 PM: >>>Given that if cygwin was this broken all sorts of other things would be >>>broken as well, this is more likely a problem with bash. >> >>One reason for my guess was that I recalled

Re: Bash 3.0-2 and kill

2005-06-25 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Igor Pechtchanski on 6/24/2005 10:50 PM: >> >>Given that if cygwin was this broken all sorts of other things would be >>broken as well, this is more likely a problem with bash. > > > One reason for my guess was that I recalled discussion

Re: Bash 3.0-2 and kill

2005-06-24 Thread Igor Pechtchanski
On Fri, 24 Jun 2005, Christopher Faylor wrote: > On Fri, Jun 24, 2005 at 05:38:02PM -0400, Igor Pechtchanski wrote: > >On Fri, 24 Jun 2005, Angelo Graziosi wrote: > > > >> I have noted that when one uses > >> > >>kill -9 > >> > >> in bash 3.0-2 (test), the command kills the process but also b

Re: Bash 3.0-2 and kill

2005-06-24 Thread Christopher Faylor
On Fri, Jun 24, 2005 at 05:38:02PM -0400, Igor Pechtchanski wrote: >On Fri, 24 Jun 2005, Angelo Graziosi wrote: > >> I have noted that when one uses >> >>kill -9 >> >> in bash 3.0-2 (test), the command kills the process but also bash (even >> if one uses /bin/kill...). >> >> In bash 2.05b-17 t

Re: Bash 3.0-2 and kill

2005-06-24 Thread Igor Pechtchanski
On Fri, 24 Jun 2005, Angelo Graziosi wrote: > I have noted that when one uses > >kill -9 > > in bash 3.0-2 (test), the command kills the process but also bash (even > if one uses /bin/kill...). > > In bash 2.05b-17 that command kills only the process. > > These things happen with > >cygwi

Bash 3.0-2 and kill

2005-06-24 Thread Angelo Graziosi
I have noted that when one uses kill -9 in bash 3.0-2 (test), the command kills the process but also bash (even if one uses /bin/kill...). In bash 2.05b-17 that command kills only the process. These things happen with cygwin 1.5.16-1 cygwin 1.5.17-1 snaps. 20050615 snaps. 200