Re: [PATCH] _rl_isearch_cleanup: avoid nested execution

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025, 23:24 penguin p wrote: > > Is this with both patches applied? > > No, it was not. I’ve now applied both patch and tested again. > > I pressed for several minutes and couldn't seem to trigger segfault. > > I think it is now fixed! > > Thank you for your help!! I can now rest

Re: [PATCH] _rl_isearch_cleanup: avoid nested execution

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025, 23:08 penguin p wrote: > I’ve applied your patch and tried again. Now it does this > > ``` > This is workbench@ArchLinux: ~/works/bash > $ ^C > This is workbench@ArchLinux: ~/works/bash > $ ^C > This is workbench@ArchLinux: ~/works/bash >

Re: [PATCH] _rl_isearch_cleanup: avoid nested execution

2025-08-17 Thread penguin p
> > 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

[PATCH] _rl_isearch_cleanup: avoid nested execution

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025 at 2:04 PM penguin p wrote: > [...] > 5 bash 0x100ca36e8 update_line + 9096 (display.c:2133) > 6 bash 0x100c9b2dc rl_redisplay + 27264 (display.c:1368) > 7 bash 0x100ca8924 rl_clear_message + 128 (display.c:3194) > 8 bash 0x100c93ab0 _rl_isearch_fini + 2396 (isea

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread penguin p
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

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread penguin p
> 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

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025 at 2:28 PM penguin p wrote: > > > >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@ma

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread penguin p
> >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

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025 at 2:04 PM penguin p wrote: > > > Penguin: > > > > Can you try building bash with AddressSanitizer and provide the crash report > > printed to the terminal from such a build? > > > > [...] > > Since you said we should move the conversions into here. I’m going to post > the fu

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread penguin p
> 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

Re: Ctrl + R, then Ctrl + C seg fault

2025-08-17 Thread Grisha Levit
On Sun, Aug 17, 2025 at 1:11 AM Grisha Levit wrote: > > On Sat, Aug 16, 2025 at 10:43 AM penguin p wrote: > > > > 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 p