Dear all, I encounter the similar problem (cvpcb crash) after switched to Nov 29 RC2 release. I don't have the development environment established so I look for the quickest (and dirtiest) fix. I found there are newer built executables in ftp://iut-tice.ujf-grenoble.fr/cao/kicad/winexe/
Replacing the exe's from Nov 29 RC2 built with those in the above URL can get rid of the (cvpcb) crashing problem, but another problem is that each time a netlist is updated using cvpcb.exe (e.g. a footprint is changed), the format generated is incorrect. The netlist will be read as a mess by pcbnew. Opened by cvpcb again I find the components' reference become the components' value, the components' value column is blank, and the footprints' reference become the components' reference. Opening the eeschema and generate the netlist again will fix the problem. I am not using Kicad very handily but I can remember this (cvpcb corrupts netlist at saving) does not occur in the previous release. Am I missing something or there are new features in the coming release? Currently I can't determine which is the better choice: 1. Change back to version before Nov 29 RC2 to get rid of cvpcb crash; 2. Use the non-official exe's from above URL You kind advice is appreciate. Regards, Patrick --- In [email protected], "daystar1013" <[EMAIL PROTECTED]> wrote: > > I believe this is related to a windows only bug in the > FootprintListBox constructor. CVPCB will crash because of the use of > an unitialized pointer in the constructor. > > the fix is to add the line > > m_ActiveFootprintList = NULL; > to the constructor, line 74 cvpcb/listboxes.cpp > > the error occurs in SetActiveFootprintList ... > > #ifdef __WINDOWS__ > /* Workaround for a curious bug in wxWidgets: > * if we switch from a long list of footprints to a short list > (a filtered footprint list), > * and if the selected item is near the end of the long list, > * the new list is not displayed from the top of the list box > */ > if ( m_ActiveFootprintList ) > { > bool new_selection; > if( FullList ) new_selection = TRUE; > else new_selection = FALSE; > if( new_selection != old_selection ) > SetSelection( 0, TRUE ); // the exception > occurs here > } > --- In [email protected], jean-pierre charras - INPG <jean- > pierre.charras@> wrote: > > > > ahuitzot a écrit : > > > > > > Since I can't get the yahoo groups search function to work, Ill > just > > > go ahead and post this... I'm sorry if its a duplicate question. > > > > > > I was working on a project 2 days ago, a simple power supply > board. > > > Everything was going ok, until I decided I would add a > hierarchical > > > sheet to my schematic. Before I did that I had added several > > > components to the schematic one at a time and used cvpcb to add > them > > > to the board, with great success. I like to do incremental adds to > > > keep from cluttering up the board, so this is why I do it this > way... > > > > > > Well anyway, I added the hierarchical sheet and put a LPC2368 on > it > > > from the nxp library I downloaded, and added 2 global net labels. > I > > > also added the same 2 global labels on the main sheet (Is that the > > > right way to do it?) I then went to re-annotate my schematic (s) > and > > > create the netlist. This all went ok as it normally had. Next I > ran > > > (or rather tried to run) cvpcb to assign the footprints to the new > > > parts. BAM it crashed right away. > > > > > Can you send me (or/and send to Dick H.) your files (zip your > project > > and send the zipped file). > > > > -- > > Jean-Pierre CHARRAS > > Maître de conférences > > Directeur d'études 2ieme année. > > Génie Electrique et Informatique Industrielle 2 > > Institut Universitaire de Technologie 1 de Grenoble > > BP 67, 38402 St Martin d'Heres Cedex > > > > Recherche : > > Grenoble Image Parole Signal Automatique (GIPSA - INPG) > > 46, Avenue Félix Viallet > > 38031 Grenoble Cedex > > >
