gnupic: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
Subject:
Re: I'm crashing the GUI in gpsim 0.20.X. Any ideas?
From:
Scott Dattalo ####@####.####
Date:
5 Oct 2001 06:34:43 -0000
Message-Id: <Pine.LNX.4.33.0110042327171.6782-100000@ruckus.brouhaha.com>
On Thu, 4 Oct 2001, Byron A Jeff wrote:
> >
> > >
> > > Any clues where I should start looking?
> >
> > Try running gpsim with --sync, and see if it gives you a better backtrace.
> > This will make gtk less smart and more direct.
>
> No change. Here's the backtrace:
>
> -------------------------------------------------------------
> Program received signal SIGSEGV, Segmentation fault.
> 0x40085f04 in XrefObject::add (this=0x80d78a0, xref=0x80fc718)
> at /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/../../../../include/g++-3/stl_list.h:347
> 347 ((_Node*) (__position._M_node->_M_prev))->_M_next = __tmp;
> (gdb) bt
> #0 0x40085f04 in XrefObject::add (this=0x80d78a0, xref=0x80fc718)
> at /usr/lib/gcc-lib/i386-slackware-linux/2.95.3/../../../../include/g++-3/stl_list.h:347
> #1 0x40063d19 in gpsim_assign_program_xref (processor_id=1, address=490,
> xref=0x80fc718) at interface.cc:666
^^^
-----------------------------------|
Hah! Caught it! Try putting a comment on line 666.
Actually, the problem is that the value for "address" is bad. I'm afraid
Philip is right; the cause is at another point in the code. If you don't
mind, send me a copy of your .asm source and I'll dive into.
Scott
