Our user reported (and I confirmed): while within the rpcclient shell pushing the tab key two times leads to a segfault if no completion is possible. e.g. there is no rpcclient command starting with the letter b, so typing b and tab leads to the following error message: pcclient $> *** glibc detected *** rpcclient: free(): invalid pointer: 0xb80a3e30 *** ======= Backtrace: ========= /lib/i686/cmov/libc.so.6(+0x6b281)[0xb77a7281] /lib/i686/cmov/libc.so.6(+0x6cad8)[0xb77a8ad8]
Created attachment 5968 [details] Patch for 3.5 This fixes it for me. Volker
Comment on attachment 5968 [details] Patch for 3.5 Looks good to me. Quick simple fix :-). Jeremy.
Re-assigning to Karolin for inclusion in 3.5.next. Jeremy.
Pushed to v3-5-test. Closing out bug report. Thanks!