Re: bash/readline spinout in vi command mode (fix identified)

2010-04-25 Thread ERIC HO
Thanks Dave for the steps to identify looping routines. Much appreciated! Eric -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simpl

Re: bash/readline spinout in vi command mode (fix identified)

2010-04-25 Thread Dave Korn
On 25/04/2010 17:01, ERIC HO wrote: > Got an update from the bash maintainer that the fix will be in the next > readline release. Good work, thanks for following through with the upstreams. > Hi Dave, in your one update that you used gdb to identify the looping > readline routines. I'd apprecia

Re: bash/readline spinout in vi command mode (fix identified)

2010-04-25 Thread ERIC HO
Got an update from the bash maintainer that the fix will be in the next readline release. Hi Dave, in your one update that you used gdb to identify the looping readline routines. I'd appreciate if you could show me the steps to do this so that I can do similar debugging myself next time. Than

Re: bash/readline spinout in vi command mode (fix identified)

2010-04-24 Thread ERIC HO
I downloaded the readline source and reviewed the looping rountines identified. It seems that the loop heappens when it is a null command line. If the command line contains some characters, the loop does not happen. I'm not a expert in C so I reported to the readline maintainer who responded wi

Re: bash/readline spinout in vi command mode

2010-04-18 Thread Dave Korn
On 18/04/2010 16:48, Andy Koppe wrote: > Spinning on a 32-bit XP here as well, whereas it didn't on a 64-bit Win7. The stack looks like this when it spins: > (gdb) bt > #0 0x61109827 in strlen () from /usr/bin/cygwin1.dll > #1 0x6afdbbb5 in rl_find_next_mbchar () from /usr/bin/cygreadline7.d

Re: bash/readline spinout in vi command mode

2010-04-18 Thread Andy Koppe
Jeremy Bopp: >> When you say spin out, do you mean it's fully loading a core? That >> would obviously be a bug, but I don't see that. For me, both with >> ESC-; and Shift-F12 it's just sitting there waiting for more input, >> which to me looks like normal operation because I do know that the >> esc

Re: bash/readline spinout in vi command mode

2010-04-17 Thread Jeremy Bopp
Changed the subject to protect the innocent... Andy Koppe wrote: > Jeremy Bopp wrote: >> On 4/17/2010 3:31 PM, ERIC HO wrote: >>> I just tested it under xterm and bash loops as well with shift F12. >> I just reproduced this problem with a simpler test case. Enter vi >> editing mode under bash an