Undelivered Mail Returned to Sender (fwd)

[Dan Langille]

bashbug fails with the following errors.  Please find attached the
original bug report.

-- 
Dan Langille - http://www.langille.org/

---------- Forwarded message ----------
Date: Wed, 17 Mar 2004 15:45:10 -0500 (EST)
From: Mail Delivery System <MAILER-DAEMON@bast.unixathome.org>
To: dan@laptop.unixathome.org
Subject: Undelivered Mail Returned to Sender

This is the Postfix program at host bast.unixathome.org.

I'm sorry to have to inform you that the message returned
below could not be delivered to one or more destinations.

For further assistance, please send mail to <postmaster>

If you do so, please include this problem report. You can
delete your own text from the message returned below.

                        The Postfix program

<bug-bash@gnu.org>: host mx10.gnu.org[199.232.76.166] said: 550-Verification
    failed for <dan@laptop.unixathome.org> 550-Unrouteable address 550 Sender
    verify failed (in reply to RCPT TO command)

Reporting-MTA: dns; bast.unixathome.org
Arrival-Date: Wed, 17 Mar 2004 15:45:09 -0500 (EST)

Final-Recipient: rfc822; bug-bash@gnu.org
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mx10.gnu.org[199.232.76.166] said:
        550-Verification failed for <dan@laptop.unixathome.org> 550-Unrouteable
        address 550 Sender verify failed (in reply to RCPT TO command)
> --- Begin Message ---
>
>
>
> Subject: 
>
> [bash cores in xterm and konsole]
>
>
>
>
> Date: 
>
> Wed, 17 Mar 2004 15:45:03 -0500 (EST)
>
>
>
>
> Configuration Information [Automatically generated, do not change]:
> Machine: i386
> OS: freebsd5.2.1
> Compiler: cc
> Compilation CFLAGS:  -DPROGRAM='bash' -DCONF_HOSTTYPE='i386' 
> -DCONF_OSTYPE='freebsd5.2.1' -DCONF_MACHTYPE='i386-portbld-freebsd5.2.1' 
> -DCONF_VENDOR='portbld'
> -DSHELL  -DHAVE_CONFIG_H  -I. -I/usr/local/include -I. -I./include -I./lib  -g3 
> -mcpu=pentiumpro
> uname output: FreeSD laptop.unixathome.org 5.2.1-RELEASE FreeBSD 5.2.1-RELEASE 
> #0: Sat Mar 13 20:42:55 EST 2004 
> dan@laptop.example.org:/usr/obj/usr/src/sys/LAPTOP  i386
> Machine Type: i386-portbld-freebsd5.2.1
>
> Bash Version: 2.05b
> Patch Level: 0
> Release Status: release
>
> Description:
> The following examples are taken directly from
> http://www.freebsd.org/cgi/query-pr.cgi?pr=ports/61297
>
> 1 - Run an xterm in XFree86 4.3.0.  Run a bash shell if you havn't already.  
> Press any of the F-keys and you'll get a bash.core dump.
>
> You may need to disable AGP in the kernel to reproduce this bug.
>
>
> 2 -  I've got the same problem as described above (on 5.2.1-p1).
>  For example, when I run blackbox using xterm and try to ALT+F2 (that's my
>  usual configuration for switching to workspace 2) while xterm is focussed
>  bash segfaults - that happens when bbkeys (which handles shortcuts to pass
>  them to the wm) is not running.
>  Another situation is when working with 'konsole' under KDE - if I press
>  shift+return at the same time 'konsole' crashes and dmesg shows:
>  "pid 659 (bash), uid 1001: exited on signal 4" - the same goes for pressing
>  the F3 and F4 buttons.
>
>
> 3 - I have similar problems with bash under FreeBSD 5.2.1 and in KDE's
>  Konsole.
>
>  Press F1 while in a bash shell in Konsole and you get:
>
>  laptpo# bash
>  [root@laptop:/home/dan] # <PRESS F1 here>Illegal instruction (core
>  dumped) laptop#
>
>  This does not happen at the console.  only Konsole.  Nor under any
>  other shell I tried (/bin/sh, /bin/csh, /bin/tcsh).
>
>  This is bash-2.05b.007
>
>  $ ldd /usr/local/bin/bash
>  ldd: /usr/local/bin/bash: not a dynamic executable
>
>  The situation is 100% reproducible here. And duplicated by others.  I have
>  since changed to a dynamic bash.  The problem remains.
>
> 4 - $ gdb /usr/local/bin/bash bash.core
>  (blah)
>  (no debugging symbols found)...
>  Core was generated by ^Bash'.
>  Program terminated with signal 4, Illegal instruction.
>
>  (gdb) bt
>  #0  0x2810b9d5 in _rl_dispatch_subseq () from /lib/libreadline.so.4
>  #1  0x2810b9be in _rl_dispatch () from /lib/libreadline.so.4
>  #2  0x2810bc28 in _rl_dispatch_subseq () from /lib/libreadline.so.4
>  #3  0x2810b9be in _rl_dispatch () from /lib/libreadline.so.4
>
>  and so on, for 2000+ lines (I stopped checking)
>
>  I'd call it a bash/readline problem, but I'm no expert
>
> Repeat-By:
>
> See above
>
> Fix:
>
> None known.
>
> --- End Message ---