kicad-developers team mailing list archive

[Dick Hollenbeck <dick@xxxxxxxxxxx>]

Thanks Blair,

I am working on these now.  It will require more than one pass to nail all of them.

I will let you know when the first pass is done.

In the second pass, please state more clearly how you are launching each program:


a) commandline with schematic in argv[1]
b) command line with no argv[1], menu driven schematic load.
c) picking a schematic from kicad prj-mgr, chain loading eeschema

You can simply refer to the letter, don't bother until pass 2.

Dick


On 03/20/2014 10:18 PM, Blair Bonnett wrote:
> Hi Dick,
> 
> 
>     I committed milestone A) this evening.
>     I will watch my email tomorrow for problem reports and calls for help.
> 
> 
> 
> On building revision 4761 on Ubuntu 13.04 (GCC 4.7.3) I got the following error:
> 
> [ 31%] Building CXX object common/CMakeFiles/common.dir/kiway_holder.cpp.o
> /home/blair/sources/kicad/product/common/kiway_holder.cpp: In member function ‘void
> KIWAY_HOLDER::SetKiway(wxWindow*, KIWAY*)’:
> /home/blair/sources/kicad/product/common/kiway_holder.cpp:18:25: error: must #include
> <typeinfo> before using typeid
> 
> I did as it says and added #include <typeinfo> to common/kiway_holder.cpp and then the
> compilation succeeds.
> 
> If I run it with an existing project, then eeschema opens and seems to work normally,
> except when I close it the following message is output in the terminal I ran kicad from:
> 
>     Error in `/usr/local/bin/eeschema': corrupted double-linked list
> 
> And the process is left running, even after I have closed the main KiCad window. Pcbnew
> works and there are no error messages. Cvpcb and gerbview do not open; I just get the
> opened and closed messages in the terminal I ran KiCad from:
> 
>     gerbview opened [pid=22596]
>     gerbview closed [pid=22596]
>     cvpcb opened [pid=22607]
>     cvpcb closed [pid=22607]
> 
> There are no error messages printed to the controlling terminal.
> 
> 
> On running KiCad with a blank project, none of eeschema, pcbnew, cvpcb, or gerbview will
> open -- just the same opened and closed messages as before, and no stderr messages printed
> to the terminal.The other tools (Bitmap2Component, PL editor, and PCB calculator) all
> appear to be OK in both cases.
> 
> If I run eeschema directly from the command line, it opens fine with a blank new schematic.
> 
> To debug, I used strace to see what was happening:
> 
>     $ strace -f -e trace=signal -e trace=file kicad
> 
> When I tried to open eeschema, the end of the output was:
> 
> [pid 22855] stat("/tmp/kicad-test-pro/foo.sch", 0x7fffc5db9090) = -1 ENOENT (No such file
> or directory)
> [pid 22855] --- SIGSEGV (Segmentation fault) @ 0 (0) ---
> Process 22855 detached
> 
> which suggests it doesn't handle missing files (as happens with a blank new project). So I
> ran eeschema standalone, saved an empty schematic as the /tmp/kicad-test-pro/foo.sch file
> it was trying to open, and it worked from within the KiCas manager. It was the same thing
> with pcbnew -- save an empty PCB using standalone pcbnew and then it will work from within
> the KiCad manager.
> 
> Using strace on cvpcb didn't show anything useful -- the previous calls were open()-ing
> fonts etc successfully, and then it just segfaulted. Running it standalone, I got it to
> dump a core. I have attached the backtrace; the core file itself is 30MB but I can upload
> it somewhere if that is usable on your system (and if it is of any use). 
> 
> I also attached GDB to the eeschema process left open after the "corrupted double-linked
> list" error I mentioned above, and have attached the backtrace from where it has frozen.
> 
> Let me know if there are any other tests or anything you would like me to run.
> 
> Blair