Follow-up Comment #19, bug #42782 (project gnustep):
Sorry for mixing the two issues. You are right about Vindaloo.
Unfortunately the Gorm backtrace is unlikely to be of any use:
Starting program: /usr/bin/Gorm
/usr/lib/GNUstep/Applications/Ink.app/Resources/Document.gorm/
[Thread debugging using libthread_db enabled]
Using host libthread_db library
"/lib/i386-linux-gnu/i686/cmov/libthread_db.so.1".
2014-07-25 12:51:42.026 Gorm[2165] Tiff Error (GSTiffReadData) Not a TIFF or
MDI file, bad magic number 20039 (0x4e47)
2014-07-25 12:51:42.057 Gorm[2165] Tiff Error (GSTiffReadData) Not a TIFF or
MDI file, bad magic number 20039 (0x4e47)
Program received signal SIGSEGV, Segmentation fault.
0x09ae01d1 in ?? ()
(gdb) bt
Python Exception <class 'gdb.MemoryError'> Cannot access memory at address
0x5:
#0 0x09ae01d1 in ?? ()
Cannot access memory at address 0x5
With your recent Gorm change I observe the behavior described in comment#6.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42782>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-gnustep mailing list
[email protected]
https://lists.gnu.org/mailman/listinfo/bug-gnustep
