On 9/20/15 4:59 PM, r...@endoria.net wrote:
> When using HISTTIMEFORMAT and a timestamp which is out of range bash seems to
> segfault. I've tested this with bash version 4.3.30(1)-release
> (x86_64-pc-linux-gnu) on Debian 8 stable.
>
> Here is how to reproduce:
> * Change (or add) a timestamp i
When using HISTTIMEFORMAT and a timestamp which is out of range bash seems to
segfault. I've tested this with bash version 4.3.30(1)-release
(x86_64-pc-linux-gnu) on Debian 8 stable.
Here is how to reproduce:
* Change (or add) a timestamp in .bash_history to:
#99
* Start a new b
2015-09-20 17:12:45 +0100, Stephane Chazelas:
[...]
> I thought the termsig_handler was being invoked upon SIGINT as
> the SIGINT handler, but it is being called explicitely by
> set_job_status_and_cleanup so the problem is elsewhere.
>
> child_caught_sigint is 0 while if I understand correctly it
On 9/20/15 12:17 AM, Brian Carpenter wrote:
> I found another null ptr deref and segfault. This only seems to affect bash
> 4.4.0 as 4.2.37(1)-release and 4.2.37(1)-release only return a 'bad
> substitution' error message.
Thanks for the report. This will be fixed in the next release of bash.
Ch
[...]
> When the above code exits without printing "hi", we see this
> call stack for instance (breakpoint on kill() in gdb):
>
> #0 kill () at ../sysdeps/unix/syscall-template.S:81
> #1 0x0045dd8e in termsig_handler (sig=) at sig.c:588
> #2 0x0045ddef in termsig_handler (sig=)
2015-09-19 21:28:24 -0400, Chet Ramey:
> On 9/19/15 5:31 PM, Stephane Chazelas wrote:
> > 2015-09-19 16:42:28 -0400, Chet Ramey:
> > [...]
> >> I'm surprised you've managed to avoid the dozen or so discussions on the
> >> topic.
> >>
> >> http://lists.gnu.org/archive/html/bug-bash/2014-03/msg00108.
