On 2015-03-19 14:38-0700 Alan W. Irwin wrote:
Hi Andrew (again):
I just discovered this issue was a regression compared to 5.10.0. So
I will git bisect it to see which commit first created this issue, and
get back to you at that point if I cannot figure out the problem
introduced by that
On Thu, Mar 19, 2015 at 09:08:21AM +, Andrew Ross wrote:
The attached patch fixes the memory leak for me. Pressing the close button
should now behave the same as pressing 'Q', i.e. it will abort the
program and clean up correctly. It looks like this was changed at some
stage in the
Great! That confirms we are looking at exactly the same bug. Thanks for
the prompt response. I think I now know how to fix it. The same issue also
seems to occur with the xcairo driver.
Andrew
On Thu, Mar 19, 2015 at 02:08:38AM -0700, Norman Goldstein wrote:
During my testing, I was using the
During my testing, I was using the close button (X) to close the window.
Just now, I reran the xwin test by hitting return to close the window,
and this produced a core dump!
Thanks for looking into all this stuff. Let me know if I can
help.
Regards,
Norm
On 03/19/2015 01:56 AM, Andrew
On 03/19/2015 09:53 AM, Jim Dishaw wrote:
Would you run the example in the debugger and set a breakpoint in plP_text
and send me a hexdump of the contents of *string? A backtrace would also be
handy.
We're choking on the cyrillic text in x33c.
Here's an example:
Breakpoint 1, plP_text
On 03/19/2015 03:30 PM, Hazen Babcock wrote:
From: Andrew Ross andrewr...@users.sourceforge.net
The attached patch fixes the memory leak for me. Pressing the close
button
should now behave the same as pressing 'Q', i.e. it will abort the
program and clean up correctly. It looks like this was
On Thu, Mar 19, 2015 at 03:30:21PM -0400, Hazen Babcock wrote:
From: Andrew Ross andrewr...@users.sourceforge.net
The attached patch fixes the memory leak for me. Pressing the close button
should now behave the same as pressing 'Q', i.e. it will abort the
program and clean up correctly.
I agree, I don't see that plplot would need to spin or in any other way
manipulate the 3d plots. It would be up to the programmer to have the
GL context wrapped in a 3D GL viewer, for example, if that kind of
functionality is desired.
On 03/19/2015 12:03 PM, Hazen Babcock wrote:
From: Norman
Hi Andrew:
I just discovered another issue which may be release critical.
For the -DENABLE_DYNDRIVERS=OFF case (with everything else default so
this issue occurs when qt_example is built against the system Qt4
libraries), the usual test_interactive target generated a glibc double
free error
On Mar 19, 2015, at 4:03 PM, Andrew Ross andrewr...@users.sourceforge.net
wrote:
On Thu, Mar 19, 2015 at 03:30:21PM -0400, Hazen Babcock wrote:
From: Andrew Ross andrewr...@users.sourceforge.net
The attached patch fixes the memory leak for me. Pressing the close button
should now behave
Hi Andrew (again):
I just discovered this issue was a regression compared to 5.10.0. So
I will git bisect it to see which commit first created this issue, and
get back to you at that point if I cannot figure out the problem
introduced by that commit.
Alan
__
Alan W.
On 03/18/2015 10:48 PM, Jim Dishaw wrote:
On Mar 18, 2015, at 11:18 PM, Orion Poplawski or...@cora.nwra.com wrote:
The check in the plplot package for the octave bindings is failing in
Fedora rawhide. I point my finger at gcc 5.0.0 :), but I have no idea
what is going on so just putting
12 matches
Mail list logo
