Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.bash.bug > #15531
| From | Eduardo Bustamante <dualbus@gmail.com> |
|---|---|
| Newsgroups | gnu.bash.bug |
| Subject | Re: Seg history |
| Date | 2019-10-22 15:33 -0700 |
| Message-ID | <mailman.1504.1571783652.9715.bug-bash@gnu.org> (permalink) |
| References | <84EF0D3A-F26B-45B0-AF93-99B4C4784A0C@gmail.com> <CAOSMAuvMdubC3EdfD=Zcs_CWCQNUEEBJPAUL87UP67eMqLwsqw@mail.gmail.com> |
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?
Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread
Re: Seg history Eduardo Bustamante <dualbus@gmail.com> - 2019-10-22 15:33 -0700
csiph-web