Karel Kulhavy wrote:
> Try to recompiling the PCB with the -g option.
Hmm, pcb magician Harry Eaton already tracked down the trigger of the
segfault. It was an empty text string, that was placed beyond the
boundaries of the working area.
I think, I will spare the hassles of recompiling pcb for th
On Sun, Mar 12, 2006 at 10:20:57PM -0500, Harry Eaton wrote:
> kmk wrote:
>
> >Hi,
> >if I try to use any of the autorouting features of pcb with my
> >PID-project, the program segfaults immediately.
> >
>
> The problem stems from the copper text appearing on the "component"
> layer. Admittedly
On Sun, Mar 12, 2006 at 09:55:59PM +0100, kmk wrote:
> Karel Kulhavy wrote:
>
> > Do:
> > ulimit -c unlimited
> > rm core*
> > reproduce the error
>
> ok, did that.
>
>
> > gdb `which pcb-bin` core*
>
> I get:
>
> GNU gdb 6.3-debian
>
> This GDB was configured as "i386-linux"...(
Harry Eaton wrote:
> solution for you is to use a text editor to remove the offending "text"
> (the one at 303567, 165071) -while you're at it, remove the other 3 null
> texts.
Did it and pcb does not segfault anymore :-)
> Now if PCB created these null texts, that's a problem.
It did. I did
kmk wrote:
Hi,
if I try to use any of the autorouting features of pcb with my
PID-project, the program segfaults immediately.
The problem stems from the copper text appearing on the "component"
layer. Admittedly the string is an empty string, but it is origin point
is outside the bounds of
