Hi All,
We have been able to recreate a scenario where bash dumps core
immediately on issuing a SIGHUP to the parent process (kill -1
). On debugging, the core so generated shows exactly the
same stack trace as we had seen with the previous core. Below is the
truss output of bash
Configuration Information [Automatically generated, do not change]:
Machine: x86_64
OS: linux-gnu
Compiler: gcc
Compilation CFLAGS: -O2 -Wall -D_FORTIFY_SOURCE=2 -fstack-protector-strong
-funwind-tables -fasynchronous-unwind-tables -fstack-clash-protection
-Werror=return-type -flto=auto -g -D_GN
On 7/31/20 2:03 AM, Oğuz wrote:
> $ sleep 25
> ^Z
> [1]+ Stopped sleep 25
> $
> $ echo $(fg; jobs %)
> bash: jobs: %: no such job
> sleep 25
> $
> $ jobs
> [1]+ Running sleep 25 &
>
> What I gather from this is that bash fak
On 7/31/20 12:29 AM, Chris Dunlop wrote:
> Bash Version: 5.0
> Patch Level: 3
> Release Status: release
>
> Description:
> Bash is leaking a file descriptor.
Patches 16 and 17 deal with this. Patch 17 is the ultimate fix.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
On 7/31/20 4:14 AM, jazz_...@arcor.de wrote:
> Bash Version: 5.0
> Patch Level: 17
> Release Status: release
>
> Description: bashbug doesn't use vi as default editor
This is not a bug.
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
``Ars longa, vita brevis'' -
On 7/31/20 3:25 AM, Rishita Saha16 wrote:
> Hi All,
>
> We have been able to recreate a scenario where bash dumps core immediately
> on issuing a SIGHUP to the parent process (kill -1 ). On
> debugging, the core so generated shows exactly the same stack trace as we
> had seen with the previous co
On 7/30/20 10:43 AM, Robert Elz wrote:
> Date:Mon, 20 Jul 2020 10:11:59 -0400
> From:Chet Ramey
> Message-ID:
>
> Sorry, didn't reply to this at the time...
>
> | You can make a case for the bash/ksh tilde expansion: the word
> | expansion is ${PARAM:=WORD}, and
We are passing SIGHUP from another terminal ( not from the terminal which
has the interactive bash shell) . The terminal which has the interactive
bash closes immediately.
The scenario is we just open two terminals. In one terminal , just invoke
bash . And from another terminal pass SIGHUP to the
On 7/31/20 10:04 AM, Ayappan P2 wrote:
> We are passing SIGHUP from another terminal ( not from the terminal which
> has the interactive bash shell) . The terminal which has the interactive
> bash closes immediately.
>
> The scenario is we just open two terminals. In one terminal , just invoke
> b
On 7/31/20 9:24 AM, Chet Ramey wrote:
> On 7/31/20 4:14 AM, jazz_...@arcor.de wrote:
>
>> Bash Version: 5.0
>> Patch Level: 17
>> Release Status: release
>>
>> Description: bashbug doesn't use vi as default editor
>
> This is not a bug.
The documentation is confusing (and IMHO wrong).
"If EDITO
On 7/31/20 11:05 AM, Eli Schwartz wrote:
> On 7/31/20 9:24 AM, Chet Ramey wrote:
>> On 7/31/20 4:14 AM, jazz_...@arcor.de wrote:
>>
>>> Bash Version: 5.0
>>> Patch Level: 17
>>> Release Status: release
>>>
>>> Description: bashbug doesn't use vi as default editor
>>
>> This is not a bug.
>
> The d
On 7/31/20 11:15 AM, Chet Ramey wrote:
> On 7/31/20 11:05 AM, Eli Schwartz wrote:
>> On 7/31/20 9:24 AM, Chet Ramey wrote:
>>> On 7/31/20 4:14 AM, jazz_...@arcor.de wrote:
>>>
Bash Version: 5.0
Patch Level: 17
Release Status: release
Description: bashbug doesn't use vi as d
31 Temmuz 2020 Cuma tarihinde Chet Ramey yazdı:
> On 7/31/20 2:03 AM, Oğuz wrote:
> > $ sleep 25
> > ^Z
> > [1]+ Stopped sleep 25
> > $
> > $ echo $(fg; jobs %)
> > bash: jobs: %: no such job
> > sleep 25
> > $
> > $ jobs
> > [1]+ Running
On 2020-07-31 at 11:26 -0400, Eli Schwartz wrote:
> In the sentence in the bashbug manpage, does the word "default" refer to
> the probing or what happens when probing fails?
>
> My belief is that people reading the manpage will understand it to mean
> the former (more natural reading).
>
> Your
On 2020-07-31 at 10:13 -0400, Chet Ramey wrote:
>
> I'm going to have to test some more. When I tried it, all the shells
> died.
> (I did send the SIGHUP from another terminal.) I was using ksh93 as
> the parent and bash-5.0.18 as the interactive bash, running on macOS.
This is probably AIX-speci
Chet Ramey writes:
>> "If EDITOR is not set, bashbug attempts to locate a number of
>> alternative editors, including emacs, and defaults to vi."
>>
>> The word "defaults" there implies that vi is the preferred autolocated
>> editor, but the intention is to have it the least preferred.
>
> I don'
16 matches
Mail list logo
