bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bash bug with ints beyond 2147483646


From: Andreas Schwab
Subject: Re: Bash bug with ints beyond 2147483646
Date: Thu, 04 Nov 2010 13:21:21 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (gnu/linux)

Marc Herbert <Marc.Herbert@gmail.com> writes:

> #0  __lll_lock_wait_private () at 
> ../nptl/sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:97
> #1  0x000000323007c138 in _L_lock_9162 () at malloc.c:3503
> #2  0x0000003230079a32 in __libc_malloc (bytes=215557320320) at malloc.c:3657
> #3  0x00000000004664c3 in xmalloc (bytes=35) at xmalloc.c:112
> #4  0x000000000049f54e in history_filename (filename=0x16bc750 
> "/raid0/home/mherbert/.bash_history") at histfile.c:120
> #5  0x000000000049f62b in history_do_write (filename=<value optimized out>, 
> nelements=1, overwrite=<value optimized out>) at histfile.c:438
> #6  0x000000000045a579 in maybe_save_shell_history () at bashhist.c:425
> #7  0x000000000045277b in termsig_handler (sig=11) at sig.c:525
> #8  <signal handler called>

This is definitely a bug in bash.  It calls functions in the signal
handler that are not async-signal-safe.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



reply via email to

[Prev in Thread] Current Thread [Next in Thread]