search for: dwarf1

One other thing that may or may not illuminate the situation. When I run under gdb (on OS X 10.8.3 this is an ancient version of gdb 6.3.5 - but it works with clang compiled C++ code) I get the following error when I try to list a line in dwarf1.lsp: Dwarf Error: Cannot handle DW_FORM_<unknown> in DWARF reader [in module /Users/meister/Development/cando/src/tests/core/dwarf1.bundle] (gdb) ---------- full gdb transcript follows ---------- (gdb) run Reading symbols for shared libraries ++++++++++++++++++++++...........................

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 describes the test case is at: https://dl.dropboxusercontent.com/u/6229900/dwarf1_new.txt I did have to make a few changes to my code to make it work with the latest llvm....

...nto it I don't seem to be able to access the metadata properly. I can list source lines using "l -f dwarf0.lsp -l 1" but I can't set break-points or do much else. I've prepared a test case and put it in my public folder on dropbox: https://dl.dropboxusercontent.com/u/6229900/dwarf1.txt It's a flat text file containing six sections which you can jump to by searching for "SECTION" (all caps). I've added a few lines at each SECTION entry with thoughts about what might be wrong or what is going on. If one of you debugging gurus could take a few minutes to take...

...eem to be able to access the metadata properly. > > I can list source lines using "l -f dwarf0.lsp -l 1" but I can't set break-points or do much else. > > I've prepared a test case and put it in my public folder on dropbox: https://dl.dropboxusercontent.com/u/6229900/dwarf1.txt > > It's a flat text file containing six sections which you can jump to by searching for "SECTION" (all caps). > I've added a few lines at each SECTION entry with thoughts about what might be wrong or what is going on. > > If one of you debugging gurus could t...

...adata properly. >> >> I can list source lines using "l -f dwarf0.lsp -l 1" but I can't set >>break-points or do much else. >> >> I've prepared a test case and put it in my public folder on dropbox: >>https://dl.dropboxusercontent.com/u/6229900/dwarf1.txt >> >> It's a flat text file containing six sections which you can jump to by >>searching for "SECTION" (all caps). >> I've added a few lines at each SECTION entry with thoughts about what >>might be wrong or what is going on. >> >> I...