mkeeter / antimony

CAD from a parallel universe
2.1k stars 159 forks source link

Segfault upon opening .sb file #142

Closed bb010g closed 8 years ago

bb010g commented 8 years ago

On this file, antimony segfaults upon opening. Was working fine when open the first time.

--- antimony/build ‹develop* M› » gdb ./app/antimony                    
GNU gdb (GDB) 7.10
Copyright (C) 2015 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./app/antimony...(no debugging symbols found)...done.
(gdb) run ~/Dropbox/ring.sb
Starting program: /home/bb010g/src/antimony-git/src/antimony/build/app/antimony ~/Dropbox/ring.sb
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffe9b3e700 (LWP 18541)]
[New Thread 0x7fffe8b0d700 (LWP 18542)]

Program received signal SIGSEGV, Segmentation fault.
0x00000000004a4445 in Port::paintRect() const ()
mkeeter commented 8 years ago

Confirmed; this looks like it was introduced in this commit.

You can roll back to before that commit and get work done; otherwise, I'll check this out tonight.