[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #42782] Crash when loading a gorm file
From: |
Yavor Doganov |
Subject: |
[bug #42782] Crash when loading a gorm file |
Date: |
Sun, 20 Jul 2014 16:32:39 +0000 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/35.0.1916.153 Safari/537.36 |
Follow-up Comment #4, bug #42782 (project gnustep):
==15741== Command: Gorm
/tmp/viewpdf.app-0.2dfsg1/English.lproj/Document.gorm/
==15741==
2014-07-20 19:27:38.764 Gorm[15741] Tiff Error (GSTiffReadData) Not a TIFF or
MDI file, bad magic number 20039 (0x4e47)
2014-07-20 19:27:42.187 Gorm[15741] Tiff Error (GSTiffReadData) Not a TIFF or
MDI file, bad magic number 20039 (0x4e47)
==15741== Conditional jump or move depends on uninitialised value(s)
==15741== at 0x408C385: _i_GormImage__initWithData_withFileName_inWrapper_
(in /usr/lib/gorm.app/libGormCore.so.1.2.20)
==15741== by 0xB3A875F: ???
==15741==
vex x86->IR: unhandled instruction bytes: 0xF0 0x5A 0x3A 0xB
==15741== Use of uninitialised value of size 4
==15741== at 0xB3A8762: ???
==15741==
==15741== Invalid read of size 1
==15741== at 0xB3A8762: ???
==15741== Address 0x134c0a52 is not stack'd, malloc'd or (recently) free'd
==15741==
==15741==
==15741== Process terminating with default action of signal 11 (SIGSEGV)
==15741== Access not within mapped region at address 0x134C0A52
==15741== at 0xB3A8762: ???
==15741== If you believe this happened as a result of a stack
==15741== overflow in your program's main thread (unlikely but
==15741== possible), you can try to increase the size of the
==15741== main thread stack using the --main-stacksize= flag.
==15741== The main thread stack size used in this run was 8388608.
==15741==
==15741== HEAP SUMMARY:
==15741== in use at exit: 9,972,293 bytes in 71,858 blocks
==15741== total heap usage: 1,228,610 allocs, 1,156,752 frees, 105,972,400
bytes allocated
==15741==
==15741== LEAK SUMMARY:
==15741== definitely lost: 37,671 bytes in 1,025 blocks
==15741== indirectly lost: 62,465 bytes in 4,126 blocks
==15741== possibly lost: 6,784,244 bytes in 27,296 blocks
==15741== still reachable: 3,087,913 bytes in 39,411 blocks
==15741== suppressed: 0 bytes in 0 blocks
==15741== Rerun with --leak-check=full to see details of leaked memory
==15741==
==15741== For counts of detected and suppressed errors, rerun with: -v
==15741== Use --track-origins=yes to see where uninitialised values come from
==15741== ERROR SUMMARY: 3 errors from 3 contexts (suppressed: 1 from 1)
Нарушение на разделянето(segfault)
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?42782>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/16
- [bug #42782] Crash when loading a gorm file, Sebastian Reitenbach, 2014/07/16
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/16
- [bug #42782] Crash when loading a gorm file, Fred Kiefer, 2014/07/19
- [bug #42782] Crash when loading a gorm file,
Yavor Doganov <=
- [bug #42782] Crash when loading a gorm file, Fred Kiefer, 2014/07/21
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/21
- [bug #42782] Crash when loading a gorm file, Fred Kiefer, 2014/07/23
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/23
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/23
- [bug #42782] Crash when loading a gorm file, Fred Kiefer, 2014/07/23
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/23
- [bug #42782] Crash when loading a gorm file, Fred Kiefer, 2014/07/24
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/24
- [bug #42782] Crash when loading a gorm file, Yavor Doganov, 2014/07/24