From: Wayne E. H. <wh...@pa...> - 2007-10-03 02:55:14
|
Eric Firing wrote: > If a straightforward plotting sequence, such as one of the examples, > does this, then it sounds like a broken installation, not a matplotlib > bug. > Based on your comment above, here are my particulars: 1) System is LinuxFromScratch recently built from their SVN book: glibc is 2.5, gcc is 4.1.2, X is Xorg 7.2 installed in /usr. 2) Python 2.5.1 with Tkinter enabled. If I run the following script, I get the 'quit' button which when clicked makes the button/window disappear, so I know python and Tkinter are working. #!/usr/bin/python from Tkinter import * class Application(Frame): def __init__(self, master=None): Frame.__init__(self, master) self.grid() self.createWidgets() def createWidgets(self): self.quitButton = Button ( self, text="Quit",command=self.quit ) self.quitButton.grid() app = Application() app.master.title("Sample application") app.mainloop() 3) Numpy 1.0.3.1 installed without any errors and I can do the following: >>> import numpy >>> List = dir(numpy) >>> len(List) 491 >>> 4) Matplotlib 0.90.1 also installed without error. I set BUILD_TKAGG = 1 which may not have been necessary, but it seems to have worked since in my matplotlibrc file I find "backend : TkAgg". Then if I do this " python simple_plot.py --verbose-debug", I get the output in the simple_output attachment. The font errors there are the same as what I get in each of my 3 XP installations where matplotlib works just fine, so I don't think they are the cause of the segfault. As I may have described previously, the plot window appears for a fraction of a second and then disappears as the segfault occurs. I also ran "strace python simple_plot.py --verbose-debug" with the output that's in the strace_output attachment to see if that would give any more information but that output ends at the segfault and I am not knowledgeable enough to understand what it says. Any help will be appreciated. Best Regards, Wayne |