On 2015-03-21 11:57-0700 Alan W. Irwin wrote:
> Hi Andrew:
>
> I have now (commit fa0c879) solved this release-critical regression.
>
> The crux of the problem is redundant linking of qt_example to both
> plplot (which contained all of the code in plplotqt for this
> ENABLE_DYNDRIVERS=NO case) and
Alan,
Thanks for the update. I'm glad you managed to track it down. I'd held of
delving into this as you seemed to have it under control. I'm also
slightly surprised at the linker not being more intelligent here.
Certainly something we need to be wary of.
Andrew
On Sat, Mar 21, 2015 at 11:57:20
Hi Andrew:
I have now (commit fa0c879) solved this release-critical regression.
The crux of the problem is redundant linking of qt_example to both
plplot (which contained all of the code in plplotqt for this
ENABLE_DYNDRIVERS=NO case) and plplotqt. examples/c++/qt_example had no severe
memory man
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 t
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. Irwin
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 messa
