[Top][All Lists]

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

Re: how to crash bash in two easy ways

From: Christopher Roy Bratusek
Subject: Re: how to crash bash in two easy ways
Date: Mon, 22 Feb 2010 16:20:42 +0100

Am Mon, 22 Feb 2010 02:30:32 -0800 (PST)
schrieb pbr <address@hidden>:

> bashbug called sendmail, a link to exim4 which silently ignored the
> following (which is a bug in its own right) so I'll post this manually
> instead.
> I found two one-liners which crash bash.
> Configuration Information [Automatically generated, do not change]:
> Machine: x86_64
> OS: linux-gnu
> Compiler: gcc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='x86_64' -
> DCONF_OSTYPE='linux-gnu' -DCONF_MACHTYPE='x86_64-pc-linux-gnu' -
> DCONF_VENDOR='pc' -DLOCALEDIR='/usr/share/locale' -DPACKAGE='bash' -
> DSHELL -DHAVE_CONFIG_H   -I.  -I../bash -I../bash/include -I../bash/
> lib   -g -O2 -Wall
> uname output: Linux Rackspace-PBR 2.6.31-19-generic #56-Ubuntu SMP Thu
> Jan 28 02:39:34 UTC 2010 x86_64 GNU/Linux
> Machine Type: x86_64-pc-linux-gnu
> Bash Version: 4.0
> Patch Level: 33
> Release Status: release
> Description:
>         I was looking for the simplest way to clear the entire aliases
> array and found a crash bug instead.
>         I Checked a few other cases and found a second case that
> crashes bash as well.
>         Bash dies with a segmentation fault anytime I type in either
> Repeat-By:
>         Type "B A S H _ A L I A S E S =" (without spaces) and then
> enter, at the command line.
>         Or, "B A S H _ C M D S =" (without spaces) for a fun variant.
> Fix:
>         My fix is sending you guys this 'bashbug' crash report.  Then
> re-sending it so it really got to you all.
> Feel free to follow up if you have any questions.
> -pbr

I'm on. 4.1(1) and this does not happen here. So perhaps it's already fixed.



reply via email to

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