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

Groups > gnu.bash.bug > #15532 > unrolled thread

Re: Seg history

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#15532 — Re: Seg history

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.

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web