/Resending I forgot to cc bug bash
> Chet
> if a SIGINT has been received, cleanup code will be executed that leaves
> whatever readline was doing in a state that it cannot continue from.
I’m not familiar with C. So in essence, what bash was doing is like this:
1. Ctrl + R
2. readline() doing som
> Chet Ramey
> What's the exact key sequence you're inputting, and are you still sending
> ESC after ^C from your keyboard config? (And why do you do that?)
> I assume you're typing ^R^C and your keyboard is sending ^R^C^[, right?
Not exactly, when I tested Ctrl + R then Ctrl + C I was also pressi
> Thanks for your careful analysis and fix. I applied a close variant, and
> that will be in the next devel branch push.
Please let me know when the new patch is ready. I can test it for you.
>
> The following change should fix this.
> ---
> Ref: https://lists.gnu.org/archive/html/bug-bash/2025-08/msg00080.html
>
> lib/readline/isearch.c | 6 --
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/lib/readline/isearch.c b/lib/readline/isearch.c
> index 241e2ee0..10483
Sorry I can’t seem to run `generate-core-file` using gdb. It hanged for a long
time
then generated a 6.1TB file which I don’t even have this much space for.
So I manually run some gdb commands and copy them into a text file.
It would be great if you can tell me what command I should run with gdb
> Can you check that this build really used AddressSanitizer?
>
> ASAN_OPTIONS=help=1 ./bash -c :
>
> Should print a bunch of option help text if it is.
Yes, I get a lot of texts.
```
$ ASAN_OPTIONS=help=1 ./bash -c
Available flags for AddressSanitizer:
quarantine_size
- Depr
> >Sorry I meant not the Apple crash report, but the output printed to
> the terminal upon a crash. It should start with something like:
Oh ok, but it didn’t look like it has anything useful printed. Here is the
message
```
penguin@macstudio bash % ./bash --norc
bash(78229,0x1fcb120c0) malloc: nan
> Penguin:
>
> Can you try building bash with AddressSanitizer and provide the crash report
> printed to the terminal from such a build?
>
> Build bash as follows:
>
> git clone --single-branch --depth=1 git://git.savannah.gnu.org/bash.git
> cd bash
> ./configure -C --without-bash-mallo
Hi,
As title, when I press Ctrl + R to search through history, then press Ctrl + C
to cancel I get set fault immediately.
This issue seems to only happen in my pc. Others cannot reproduce, and the
homebrew team? recommended me to report in here.
This bug vanished when a debugger is attached.
