Preferred Qt4 version with 0.98.3

Hello,
I’m trying to track down a segfault when a canvas.draw() call is made in my GUI program using the Qt4Agg backend. I am running matplotlib 0.98.3 and Qt 4.3.2. I know the Qt version is a bit old, so I wanted to check if I should be suspicious of version incompatibility. I am working on a script to demonstrate the segfault.

Thanks,
Glenn

I'm using Qt 4.3.0/PyQt 4.2, compiled from source on RHEL4 with no problems, so it's not necessarily that your version is too old.

Once you have a script to reproduce and (ideally) a gdb backtrace, that should help us narrow down on the root cause.

Mike

G Jones wrote:

···

Hello,
I'm trying to track down a segfault when a canvas.draw() call is made in my GUI program using the Qt4Agg backend. I am running matplotlib 0.98.3 and Qt 4.3.2. <http://4.3.2.> I know the Qt version is a bit old, so I wanted to check if I should be suspicious of version incompatibility. I am working on a script to demonstrate the segfault.
Thanks,
Glenn
------------------------------------------------------------------------

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
------------------------------------------------------------------------

_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
  
--
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

The problem seems to be fixed after updating SIP from 4.7 from the ubuntu repositories to 4.7.7 from the source. I think it had to do with mixing threading.Thread with a Qt application, but I’m not entirely sure.

Thanks for the info anyway,
Glenn

···

On Wed, Oct 15, 2008 at 6:00 AM, Michael Droettboom <mdroe@…86…> wrote:

I’m using Qt 4.3.0/PyQt 4.2, compiled from source on RHEL4 with no problems, so it’s not necessarily that your version is too old.

Once you have a script to reproduce and (ideally) a gdb backtrace, that should help us narrow down on the root cause.

Mike

G Jones wrote:

Hello,

I’m trying to track down a segfault when a canvas.draw() call is made in my GUI program using the Qt4Agg backend. I am running matplotlib 0.98.3 and Qt 4.3.2. <http://4.3.2.> I know the Qt version is a bit old, so I wanted to check if I should be suspicious of version incompatibility. I am working on a script to demonstrate the segfault.

Thanks,

Glenn



This SF.Net email is sponsored by the Moblin Your Move Developer’s challenge

Build the coolest Linux based applications with Moblin SDK & win great prizes

Grand prize is a trip for two to an Open Source event anywhere in the world

http://moblin-contest.org/redirect.php?banner_id=100&url=/



Matplotlib-users mailing list

Matplotlib-users@lists.sourceforge.net

https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Michael Droettboom

Science Software Branch

Operations and Engineering Division

Space Telescope Science Institute

Operated by AURA for NASA