RE: cygheap base mismatch detected

2017-06-16 Thread Jon Morris
No problem. I don't have cygwin installed so the problem is something is looking for it. I've reinstalled git for windows so if the problem doesn't go away, I'll raise a defect with Cmder. Thanks, Jon -Original Message- From: Eduardo Bustamante [mailto:dual...@gmail.com] Sent: 15 June

Re: AddressSanitizer: heap-buffer-overflow in rl_delete

2017-06-16 Thread Eduardo A . Bustamante López
On Thu, Jun 15, 2017 at 09:36:58AM -0500, Eduardo Bustamante wrote: > Found by fuzzing `read -e' with AFL. The stacktrace reported by Address > Sanitizer is followed by the base64 encoded crashing input. > > > ==1736==ERROR: AddressSanitizer: heap-buffer-overflow on address > 0x61109880 at p

Re: AddressSanitizer: global-buffer-overflow in rl_filename_completion_function

2017-06-16 Thread Eduardo A . Bustamante López
On Thu, Jun 15, 2017 at 09:41:08AM -0500, Eduardo Bustamante wrote: > Found by fuzzing `read -e' with AFL. The stacktrace reported by Address > Sanitizer is followed by the base64 encoded crashing input. > > > ==1098==ERROR: AddressSanitizer: global-buffer-overflow on address > 0x55e61a6b4c5c at

Re: AddressSanitizer: heap-buffer-overflow in rl_tilde_expand

2017-06-16 Thread Eduardo A . Bustamante López
On Thu, Jun 15, 2017 at 09:39:09AM -0500, Eduardo Bustamante wrote: > Found by fuzzing `read -e' with AFL. The stacktrace reported by Address > Sanitizer is followed by the base64 encoded crashing input. > > > ==472==ERROR: AddressSanitizer: heap-buffer-overflow on address > 0x6110977f at pc

Re: AddressSanitizer: heap-buffer-overflow in rl_kill_text

2017-06-16 Thread Eduardo A . Bustamante López
On Thu, Jun 15, 2017 at 09:42:41AM -0500, Eduardo Bustamante wrote: > Found by fuzzing `read -e' with AFL. The stacktrace reported by Address > Sanitizer is followed by the base64 encoded crashing input. > > > ==11018==ERROR: AddressSanitizer: heap-buffer-overflow on address > 0x6070ccc0 at

Re: AddressSanitizer: heap-buffer-overflow in rl_delete

2017-06-16 Thread Chet Ramey
On 6/16/17 10:27 AM, Eduardo A. Bustamante López wrote: > On Thu, Jun 15, 2017 at 09:36:58AM -0500, Eduardo Bustamante wrote: >> Found by fuzzing `read -e' with AFL. The stacktrace reported by Address >> Sanitizer is followed by the base64 encoded crashing input. >> >> >> ==1736==ERROR: AddressSani

Re: AddressSanitizer: heap-buffer-overflow in rl_tilde_expand

2017-06-16 Thread Chet Ramey
On 6/16/17 10:43 AM, Eduardo A. Bustamante López wrote: > On Thu, Jun 15, 2017 at 09:39:09AM -0500, Eduardo Bustamante wrote: >> Found by fuzzing `read -e' with AFL. The stacktrace reported by Address >> Sanitizer is followed by the base64 encoded crashing input. >> >> >> ==472==ERROR: AddressSanit

Re: AddressSanitizer: global-buffer-overflow in rl_filename_completion_function

2017-06-16 Thread Chet Ramey
On 6/16/17 10:57 AM, Eduardo A. Bustamante López wrote: > On Thu, Jun 15, 2017 at 09:41:08AM -0500, Eduardo Bustamante wrote: >> Found by fuzzing `read -e' with AFL. The stacktrace reported by Address >> Sanitizer is followed by the base64 encoded crashing input. >> >> >> ==1098==ERROR: AddressSani

Re: AddressSanitizer: heap-buffer-overflow in rl_kill_text

2017-06-16 Thread Chet Ramey
On 6/16/17 11:10 AM, Eduardo A. Bustamante López wrote: > On Thu, Jun 15, 2017 at 09:42:41AM -0500, Eduardo Bustamante wrote: >> Found by fuzzing `read -e' with AFL. The stacktrace reported by Address >> Sanitizer is followed by the base64 encoded crashing input. >> >> >> ==11018==ERROR: AddressSan

Re: Why does 'connect' take so long (sometimes) and can't be interrupted?

2017-06-16 Thread Chet Ramey
On 6/15/17 11:36 AM, gaze...@xmission.com wrote: > Note, however, that it does eventually connect. As far as I can tell, > it > does always eventually connect. > > Needless to say, when I first hit this problem, I assumed it had hung, > and > when I tried to kill it, I