SilentFlame

interchunkDebug

May 16th, 2017
80
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.09 KB | None | 0 0
  1. from the start:
  2. speedy@Vinay:~/FLAME/Apertium/apertium$ sh autogen.sh
  3. speedy@Vinay:~/FLAME/Apertium/apertium$ make clean
  4. speedy@Vinay:~/FLAME/Apertium/apertium$ ./configure CFLAGS="-ggdb3 -O0" CXXFLAGS="-ggdb3 -O0" LDFLAGS="-ggdb3"
  5. speedy@Vinay:~/FLAME/Apertium/apertium$ make
  6.  
  7. then for gdb I either run in apertium main or apertium en-es.
  8. ## Running gdb in apertium-en-es.
  9. speedy@Vinay:~/FLAME/Apertium/apertium-en-es$ libtool --mode=execute gdb ../apertium/apertium/apertium-interchunk
  10.  
  11. inside gdb I run
  12. (gdb) run apertium-en-es.en-es.t2x en-es.t2x.bin < interchunk.input
  13.  
  14. which gives
  15. Starting program: /home/speedy/FLAME/Apertium/apertium/apertium/.libs/lt-apertium-interchunk apertium-en-es.en-es.t2x en-es.t2x.bin < interchunk.input
  16. [Thread debugging using libthread_db enabled]
  17. Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  18.  
  19. Program received signal SIGSEGV, Segmentation fault.
  20. 0x00007fffffffd988 in ?? ()
  21.  
  22. (gdb)bt ## gives
  23. #0 0x00007fffffffd988 in ?? ()
  24. #1 0x00000005f6ed98e0 in ?? ()
  25. #2 0x0000000000000000 in ?? ()
  26.  
  27. Unable to understand what to do?
Add Comment
Please, Sign In to add comment