kicad-developers team mailing list archive
Mailing list archive
Re: Re: EESchema freezes a couple minutes after start.
As the subject, I still don't know what is happening. It freezes even without being used. Can someone confirm that? I'm using kicad R2389.
Just to better focusing the problem:
On which platform that happens ?
With which wx-widgets version ?
Here is my platform:
Build: (20100223 SVN-R2389)-RC4
wxWidgets 2.8.10 Unicode on 32 Bits GNU/Linux (Archlinux)
Does eeschema has log/debug info? I would investigate the problem.
Did you compile it ? if yes with in Debug or Release ?
And how you have started eeschema ? (executing the eeschema binary directly or passing by the project manager (kicad))
Yes, I use arch building system to compile it as Release. I normally start eeschema with kicad. But I'm trying with eeschema start.
Marco, it's been about an hour without problem now. The problem seems to limit with eeschema started by kicad. I'll report again in a few hours.
Dick has answered you, this is why i've asked you in which way you have started eeschema.
Dick what about use something like wxProcess::Detach() to avoid this problem or using wxProcess::GetInputStream and destroy the Stream ?
We could read from the child's output pipe using a blocking read from
within Kicad executable, if wxWidgets provides a blocking read on this
Right now it is folk lore, but it is fairly well known now that leaving
these printf's in there should only be allowed for the debug builds.
And from that, it goes without saying that the debug builds should be
run from the command line, that is what they are for. I would never
*install* a debug build, I only run them from the command line.
But I see no harm in draining the pipe that sits between the child and
parent kicad executable, if this bothers you. It does not bother me.
(It only bothered me up to the point where I understood the problem. :) )