[sword-devel] segfault in osis2mod, showstopper, unfortunately

[scribe777@gmail.com]

Ok, we're probably in a recursive loop. The first output you gave with the stack trace from gdb, can you give more? Try to give enough to where we can recognize a repeating pattern.

Troy

Peter von Kaehne <refdoc at gmx.net> wrote:

>On 04/07/11 20:29, Troy A. Griffitts wrote:
>> Can you send me 'yo'
>
>peter at practice:~/Playground/Belarus$ cat yo
>==26546== Memcheck, a memory error detector
>==26546== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et
>al.
>==26546== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright
>info
>==26546== Command: osis2mod bela bela.osis.xml -v SynodalP
>==26546== Parent PID: 7498
>==26546==
>peter at practice:~/Playground/Belarus$ cat yo
>==26546== Memcheck, a memory error detector
>==26546== Copyright (C) 2002-2010, and GNU GPL'd, by Julian Seward et
>al.
>==26546== Using Valgrind-3.6.1 and LibVEX; rerun with -h for copyright
>info
>==26546== Command: osis2mod bela bela.osis.xml -v SynodalP
>==26546== Parent PID: 7498
>==26546==
>==26546== Stack overflow in thread 1: can't grow stack to 0xbe389fd8
>==26546==
>==26546== Process terminating with default action of signal 11
>(SIGSEGV)
>==26546==  Access not within mapped region at address 0xBE389FD8
>==26546==    at 0x4025510: operator delete[](void*)
>(vg_replace_malloc.c:409)
>==26546==  If you believe this happened as a result of a stack
>==26546==  overflow in your program's main thread (unlikely but
>==26546==  possible), you can try to increase the size of the
>==26546==  main thread stack using the --main-stacksize= flag.
>==26546==  The main thread stack size used in this run was 8388608.
>==26546== Stack overflow in thread 1: can't grow stack to 0xbe389fd4
>==26546==
>==26546== Process terminating with default action of signal 11
>(SIGSEGV)
>==26546==  Access not within mapped region at address 0xBE389FD4
>==26546==    at 0x402040C: _vgnU_freeres (vg_preloaded.c:58)
>==26546==  If you believe this happened as a result of a stack
>==26546==  overflow in your program's main thread (unlikely but
>==26546==  possible), you can try to increase the size of the
>==26546==  main thread stack using the --main-stacksize= flag.
>==26546==  The main thread stack size used in this run was 8388608.
>==26546==
>==26546== HEAP SUMMARY:
>==26546==     in use at exit: 7,407,406 bytes in 68,956 blocks
>==26546==   total heap usage: 12,551,445 allocs, 12,482,489 frees,
>714,540,196 bytes allocated
>==26546==
>==26546== LEAK SUMMARY:
>==26546==    definitely lost: 0 bytes in 0 blocks
>==26546==    indirectly lost: 0 bytes in 0 blocks
>==26546==      possibly lost: 0 bytes in 0 blocks
>==26546==    still reachable: 7,407,406 bytes in 68,956 blocks
>==26546==         suppressed: 0 bytes in 0 blocks
>==26546== Rerun with --leak-check=full to see details of leaked memory
>==26546==
>==26546== For counts of detected and suppressed errors, rerun with: -v
>==26546== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 77 from
>8)
>
>
>_______________________________________________
>sword-devel mailing list: sword-devel at crosswire.org
>http://www.crosswire.org/mailman/listinfo/sword-devel
>Instructions to unsubscribe/change your settings at above page

-- 
Sent from my Android phone with K-9 Mail. Please excuse my brevity.