[PATCH] Debugging LLVM IR with LLDB (and gdb)

[Malea, Daniel]

I'm wary of adding the testing code to the clang repos, since the pass really has nothing to do with clang… I'm going to re-visit the tests anyways, as the temporary "-debug.ll" files that "opt -debug–ir" generates caused some buildbot troubles today, so I reverted them.

Anyways, it might be that the simplest thing is to support input .ll files free of metadata. Regarding that, does anyone know of any resource/code that already exists which generates a DISubprogram node from an llvm::Function signature? Right now, that looks like it would be the most annoying part that's left to do.

Cheers,
Dan


From: Andrew Trick <atrick at apple.com<mailto:atrick at apple.com>>
Date: Wednesday, 8 May, 2013 5:20 PM
To: Daniel Malea <daniel.malea at intel.com<mailto:daniel.malea at intel.com>>
Cc: Eric Christopher <echristo at gmail.com<mailto:echristo at gmail.com>>, Chandler Carruth <chandlerc at google.com<mailto:chandlerc at google.com>>, Nadav Rotem <nrotem at apple.com<mailto:nrotem at apple.com>>, "llvm-commits at cs.uiuc.edu<mailto:llvm-commits at cs.uiuc.edu>" <llvm-commits at cs.uiuc.edu<mailto:llvm-commits at cs.uiuc.edu>>
Subject: Re: [PATCH] Debugging LLVM IR with LLDB (and gdb)


I imagine that c/c++ code needs to be in clang/test.

More importantly though, the .ll input should be free of metadata. I suggest focussing on fixing that before the debug format changes again.

There is still the issue of your CHECKed output matching the current format. But in that case, when the test breaks, someone can just copy the new output in to the CHECK file. Right?