Re: [Nano-devel] [PATCH] browser: awkward behaviour when trying to open inaccessible directory using goto prompt

[Benno Schulenberg]

On Fri, Jun 24, 2016, at 13:29, Rishabh Dave wrote:
> Valgrind points the memory leak at charealloc() after the statement
> "if (newpath[0] != '/')". Couldn't find a leak there. According to me,
> when newpath is used for goto_dir_void it has its own allocated memory
> which is never deallocated. So, along with little adjustments I
> received positive result. Patch is attached.

I can't follow your reasoning, but you made the changes I wanted
to see.  :)

That part of the patch is okay now.

However, try this:

export MALLOC_CHECK_=2
export MALLOC_PERTURB_=144
src/nano --operating=.

Then type: ^R ^T M-G /home <Enter>

Ignore the error message and type: ^L

[ Cannot open directory: File name too long ]Aborted


Hint: freeing something does not set it to null.

Benno

-- 
http://www.fastmail.com - Choose from over 50 domains or use your own