gnuplot-beta

crash on exit, on OS X

[Allin C. <cot...@wf...>]

Sorry if I've missed discussion of this, but I'm seeing a crash on 
exiting gnuplot (by typing "quit" or "q" then Enter) when running in 
Terminal.app on Mac OS X.

This is with current CVS gnuplot, OS X 10.6.8. The message I'm 
getting is:

gnuplot> q
gnuplot(19077) malloc: *** error for object 0x71: pointer being 
freed was not allocated
*** set a breakpoint in malloc_error_break to debug
Abort trap

-- 
Allin Cottrell
Department of Economics
Wake Forest University

Re: crash on exit, on OS X

[Mojca M. <moj...@gm...>]

On Tue, Mar 19, 2013 at 2:34 AM, Allin Cottrell wrote:
> Sorry if I've missed discussion of this, but I'm seeing a crash on
> exiting gnuplot (by typing "quit" or "q" then Enter) when running in
> Terminal.app on Mac OS X.
>
> This is with current CVS gnuplot, OS X 10.6.8. The message I'm
> getting is:
>
> gnuplot> q
> gnuplot(19077) malloc: *** error for object 0x71: pointer being
> freed was not allocated
> *** set a breakpoint in malloc_error_break to debug
> Abort trap

Which compiler, which terminal and what libraries did you use
(MacPorts, Fink, Homebrew or nothing)? I tried it on 10.7 with
libraries from MacPorts, but I don't experience that problem with a
couple of simple plotting commands.

Mojca

Re: crash on exit, on OS X

[Allin C. <cot...@wf...>]

On Wed, 20 Mar 2013, Mojca Miklavec wrote:

> On Tue, Mar 19, 2013 at 2:34 AM, Allin Cottrell wrote:
>> Sorry if I've missed discussion of this, but I'm seeing a crash on
>> exiting gnuplot (by typing "quit" or "q" then Enter) when running in
>> Terminal.app on Mac OS X.
>>
>> This is with current CVS gnuplot, OS X 10.6.8. The message I'm
>> getting is:
>>
>> gnuplot> q
>> gnuplot(19077) malloc: *** error for object 0x71: pointer being
>> freed was not allocated
>> *** set a breakpoint in malloc_error_break to debug
>> Abort trap
>
> Which compiler, which terminal and what libraries did you use
> (MacPorts, Fink, Homebrew or nothing)? I tried it on 10.7 with
> libraries from MacPorts, but I don't experience that problem with a
> couple of simple plotting commands.

Apple's gcc, AquaTerm, other libraries compiled from source on 
the target machine. I'll try a build with debugging enabled 
and see if I can get a better idea of what's happening. In the 
meantime I'm attaching the OS X trace in case it's any help.

-- 
Allin Cottrell
Department of Economics
Wake Forest University, NC

Re: crash on exit, on OS X

[Allin C. <cot...@wf...>]

On Mon, 18 Mar 2013, Allin Cottrell wrote:

> Sorry if I've missed discussion of this, but I'm seeing a crash on exiting 
> gnuplot (by typing "quit" or "q" then Enter) when running in Terminal.app on 
> Mac OS X.
>
> This is with current CVS gnuplot, OS X 10.6.8. The message I'm getting is:
>
> gnuplot> q
> gnuplot(19077) malloc: *** error for object 0x71: pointer being freed was not 
> allocated
> *** set a breakpoint in malloc_error_break to debug
> Abort trap

OK, I now see what's wrong: readline was crossed-up. Gnuplot's 
configure script found GNU readline under /usr/local but the build 
linked against Apple's fake readline (libedit.dylib). So bad results 
may be expected.

If I either specify --with-readline=bsd or add -L/usr/local/lib to 
CFLAGS when running configure, I get a consistent build that doesn't 
crash. I'd forgotten about the fake readline business.

Allin Cottrell

Re: crash on exit, on OS X

[Ethan A M. <sf...@us...>]

On Wednesday, March 20, 2013 03:25:01 pm Allin Cottrell wrote:
> On Mon, 18 Mar 2013, Allin Cottrell wrote:
> 
> > Sorry if I've missed discussion of this, but I'm seeing a crash on exiting 
> > gnuplot (by typing "quit" or "q" then Enter) when running in Terminal.app on 
> > Mac OS X.
> >
> > This is with current CVS gnuplot, OS X 10.6.8. The message I'm getting is:
> >
> > gnuplot> q
> > gnuplot(19077) malloc: *** error for object 0x71: pointer being freed was not 
> > allocated
> > *** set a breakpoint in malloc_error_break to debug
> > Abort trap
> 
> OK, I now see what's wrong: readline was crossed-up. Gnuplot's 
> configure script found GNU readline under /usr/local but the build 
> linked against Apple's fake readline (libedit.dylib). So bad results 
> may be expected.
> 
> If I either specify --with-readline=bsd or add -L/usr/local/lib to 
> CFLAGS when running configure, I get a consistent build that doesn't 
> crash. I'd forgotten about the fake readline business.
> Allin Cottrell

That's good to know in case someone else runs into the same symptoms.

Note, however, that gnuplot's built-in readline is probably a better option
than the BSD version.  The built-in version was extended during the 4.6
development cycle to include tab-completion.  More to the point, it was 
extended to handle UTF8 encoding, which the BSD version does not support.

	Ethan