Displaying 2 results from an estimated 2 matches for "cons_o".
Did you mean:
cons_q
2013 Apr 24
0
[LLVMdev] Questions about attaching DWARF source code debugging information to generated LLVM-IR.
.../GENERIC CLOS/FIXUP :FRONT CLOS/CONDITIONS CLOS/PRINT CLOS/STREAMS LSP/PPRINT :CLOS )
BRIDGE-COMMON-LISP (copyright Christian E. Schafmeister 2013) - 1.0
CORE>>> (defun gdb () (break "break"))
; --> #<INTERPRETED :name GDB :llh #<LAMBDA-LIST-HANDLER :ClassifiedSymbols Cons_O::nil :comment ""> :environment #[VALUE-ENVIRONMENT :id 27874
----NO METADATA----
]
:declares Cons_O::nil :docstring """" :code ((BLOCK GDB ( BREAK "break" ) ) ) >
CORE>>> (load-bundle "dwarf1.bundle")
Reading symbo...
2013 Apr 24
2
[LLVMdev] Questions about attaching DWARF source code debugging information to generated LLVM-IR.
I upgraded my versions of llvm, clang and compiler-rt to the top-of-tree versions from last night (r180162, April 24).
I recompiled debug versions of llvm, clang and my code.
I then regenerated my test case and the results were the same - I can list lines of dwarf1.lsp in lldb but I can't set break-points or do anything else (what else should I be able to do?).
The updated file that