Skip to content

Instantly share code, notes, and snippets.

@MasterDuke17
Created February 4, 2019 23:58
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save MasterDuke17/07de146b1b38456a7dfdae5eea18983e to your computer and use it in GitHub Desktop.
Save MasterDuke17/07de146b1b38456a7dfdae5eea18983e to your computer and use it in GitHub Desktop.
Starting program: /home/dan/Source/perl6/install/bin/moar --execname=/home/dan/Source/perl6/install/bin/perl6-gdb-m --libpath=/home/dan/Source/perl6/install/share/nqp/lib --libpath=/home/dan/Source/perl6/install/share/perl6/lib --libpath=/home/dan/Source/perl6/install/share/perl6/runtime /home/dan/Source/perl6/install/share/perl6/runtime/perl6.moarvm pc.p6
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7ffff6f93700 (LWP 3749)]
Compiling...
Thread 1 "moar" hit Breakpoint 1, MVM_interp_run (tc=0x555556f88576, tc@entry=0x555555559ca0, initial_invoke=0x7ffff7de8500 <LABELS.18558>, invoke_data=0x73) at src/core/interp.c:843
843 GET_REG(cur_op, 0).n64 = 1.0 / cosh(GET_REG(cur_op, 2).n64);
(gdb) bt
#0 MVM_interp_run (tc=0x555556f88576, tc@entry=0x555555559ca0, initial_invoke=0x7ffff7de8500 <LABELS.18558>, invoke_data=0x73) at src/core/interp.c:843
#1 0x00007ffff7a886c5 in MVM_vm_run_file (instance=0x555555559260, filename=<optimized out>) at src/moar.c:440
#2 0x0000555555555791 in main (argc=7, argv=0x7fffffffdda8) at src/main.c:301
(gdb) call MVM_dump_backtrace(tc)
Thread 1 "moar" received signal SIGSEGV, Segmentation fault.
0x00007ffff79c885b in MVM_gc_root_temp_push_slow (tc=0x555556f88576, obj_ref=obj_ref@entry=0x7fffffffd680) at src/gc/roots.c:224
224 tc->temproots[tc->num_temproots] = obj_ref;
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(MVM_dump_backtrace) will be abandoned.
When the function is done executing, GDB will silently stop.
(gdb)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment