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


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

Re: Seg history

Started byEduardo Bustamante <dualbus@gmail.com>
First post2019-10-22 15:33 -0700
Last post2019-10-22 15:33 -0700
Articles 1 — 1 participant

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 Eduardo Bustamante <dualbus@gmail.com> - 2019-10-22 15:33 -0700

#15531 — Re: Seg history

FromEduardo Bustamante <dualbus@gmail.com>
Date2019-10-22 15:33 -0700
SubjectRe: Seg history
Message-ID<mailman.1504.1571783652.9715.bug-bash@gnu.org>
On Tue, Oct 22, 2019 at 6:09 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)

Hi Younes,

1) What version of bash are you using? (And did you compile it
yourself or are you using a specific software distribution?)
2) What do you mean by 'seg'? Do you mean a segmentation fault? If so,
can you generate a stack trace of the crash?

[toc] | [standalone]


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


csiph-web