On Tue, May 20, 2014 at 02:48:06AM -0000, madworm wrote:
> Public bug reported:
>
> This issue was introduced after 4865, which still works fine.
OK, found another way to reproduce, too. Plot options, changing
something and then close twice gives a segfault.
#0 0x00007ffff57048d4 in free () from /lib64/libc.so.6
#1 0x00007fffee5b7d08 in wxString::~wxString() ()
from /home/lomarcan/cvswork/kicad-vnd/pcbnew/_pcbnew.kiface
#2 0x00007fffee84578f in NETCLASS::~NETCLASS() ()
from /home/lomarcan/cvswork/kicad-vnd/pcbnew/_pcbnew.kiface
#3 0x00007fffee845e1f in NETCLASSES::Clear() ()
from /home/lomarcan/cvswork/kicad-vnd/pcbnew/_pcbnew.kiface
#4 0x00007fffee845e49 in NETCLASSES::~NETCLASSES() ()
from /home/lomarcan/cvswork/kicad-vnd/pcbnew/_pcbnew.kiface
#5 0x00007fffee5d0562 in
PCB_EDIT_FRAME::ToPlotter(wxCommandEvent&) ()
from
/home/lomarcan/cvswork/kicad-vnd/pcbnew/_pcbnew.kiface
A double free or some memory stomping?
I hoped it was from the GetTrack changes but these were in 4865... are
you sure thate 4866 already has the issue? Only eeschema changed in
it...
On Tue, May 20, 2014 at 02:48:06AM -0000, madworm wrote:
> Public bug reported:
>
> This issue was introduced after 4865, which still works fine.
OK, found another way to reproduce, too. Plot options, changing
something and then close twice gives a segfault.
#0 0x00007ffff57048d4 in free () from /lib64/libc.so.6 :~wxString( ) () cvswork/ kicad-vnd/ pcbnew/ _pcbnew. kiface :~NETCLASS( ) () cvswork/ kicad-vnd/ pcbnew/ _pcbnew. kiface cvswork/ kicad-vnd/ pcbnew/ _pcbnew. kiface :~NETCLASSES( ) () cvswork/ kicad-vnd/ pcbnew/ _pcbnew. kiface FRAME:: ToPlotter( wxCommandEvent& ) () lomarcan/ cvswork/ kicad-vnd/ pcbnew/ _pcbnew. kiface
#1 0x00007fffee5b7d08 in wxString:
from /home/lomarcan/
#2 0x00007fffee84578f in NETCLASS:
from /home/lomarcan/
#3 0x00007fffee845e1f in NETCLASSES::Clear() ()
from /home/lomarcan/
#4 0x00007fffee845e49 in NETCLASSES:
from /home/lomarcan/
#5 0x00007fffee5d0562 in
PCB_EDIT_
from
/home/
A double free or some memory stomping?
I hoped it was from the GetTrack changes but these were in 4865... are
you sure thate 4866 already has the issue? Only eeschema changed in
it...
--
Lorenzo Marcantonio
Logos Srl