Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15532

Re: Seg history

From Dennis Williamson <dennistwilliamson@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: Seg history
Date 2019-10-22 18:24 -0500
Message-ID <mailman.1507.1571786709.9715.bug-bash@gnu.org> (permalink)
References <84EF0D3A-F26B-45B0-AF93-99B4C4784A0C@gmail.com> <CANaoh6KqkVcS3v79cwgq39vLe0Cg16xYdQ2jmo=g69YUiTyWgg@mail.gmail.com>

Show all headers | View raw


On Tue, Oct 22, 2019, 8:10 AM younes berramdane <younesberramdane1@gmail.com>
wrote:

> Hello,
> I have found a seg in the history of bash while I was doing a project for
> my school,
> (Put fc -s at the last command of the history file [~/.sh_history] for
> bash posix or [~/.bash_history] for bash then launch bash and execute fc -s
> again)
>
> Best regards,
> Younes Berramdane.
>

This causes fc -s to re-execute itself in a tight loop repeatedly until a
seg fault occurs.

I don't know whether Bash should catch this but it definitely falls under
"doctor, it hurts when I do this" - IOW, don't do that. Especially since it
takes extra effort to set up the necessary conditions.

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Seg history Dennis Williamson <dennistwilliamson@gmail.com> - 2019-10-22 18:24 -0500

csiph-web