Bash crash, with crash file, unreproducible

please attach the script which crashed; apparently it's a recursion eating up all the stack.

You don't happen to have the name of that script? In that case I might be able to retrieve it, but I unforturnately have no idea what I was doing at the time of the crash so without a command line I can't help you.

Or is this another instance of bug 95504? Only libc stuff in the backtrace AFAICT so this might be. How did the retrace go?

I'm not sure if this is the same, but I can crash bash with the following script:
----
#!/bin/bash
ttt() {
        ttt
}
ttt
----
Arguably, bash should not just crash with a segfault when you have an infinite loop in a bash script.

Johan, the only thing I get from your crash report is the directory you were in when this happened: /localhome/johan/clients/johan/badkar-sandbox

If this helps you find the script in question or even reproduce this bug, that would be great!

The inifinit recursion issue is already reported as #146746

Mika, this happened over a year ago, and that directory doesn't exist any more.

However, this bug report contains a crash file that somebody at Ubuntu could use to get a stack trace from the crashed bash:
http://launchpadlibrarian.net/7055251/_bin_bash.537.crash

Unfortunately, in the last 15 months nobody from Ubuntu has commented on that crash file :-(.

Until that happens I'm not interested in trying to provide more data on the crash.

Johan,

the only thing that can be gathered from the crash report is that there is an inifnite recursion, most probably caused in the script that was running. Mathias Klose mentioned that on 2007-04-06. Since bash is interpreting the script the stack trace is not very useful.

The script name is unfortunately not included in the crash report.

I tried getting something out of the coredump but since the debug symbols for this old version of bash aren't available anymore I did not get much out of it...

But if you're not experiencing this bug anymore I'm inclined to just mark it as a duplicate of bug#146746 since they seem related and the other one is easily reproducable.

Thanks for looking at the crash file!

Matthias never mentioned having looked at the crash file, so I didn't understand that he had.

Since this bug is now too old to be handled, and it is (just like you say) likely a dup of 146746 I've marked it as such.