[LLVMdev] bugpoint usage
criswell at cs.uiuc.edu
Wed Feb 21 07:45:00 PST 2007
Seung Jae Lee wrote:
> Thank you for this information.
> If so, is there any way to grasp which kinda data throw in and out in LLVM as shown in such a way in gdb?
I don't understand the question. Are you trying to debug an LLVM pass,
or are you trying to debug a program generated by LLVM?
You can use gdb on the LLVM tools (such as opt) to debug LLVM passes,
and you can run gdb on code statically compiled with the LLVM compilers,
too (although I don't know how complete the debug information will be in
the resulting executable).
-- John T.
> Seung Jae Lee
> ---- Original message ----
>> Date: Tue, 20 Feb 2007 23:54:04 -0600
>> From: "John T. Criswell" <criswell at cs.uiuc.edu>
>> Subject: Re: [LLVMdev] bugpoint usage
>> To: LLVM Developers Mailing List <llvmdev at cs.uiuc.edu>
>> Seung Jae Lee wrote:
>>> Can I use debugging options such as 'step', 'next'(in gdb) also in LLVM bugpoint?
>> I assume you're asking if you can use commands like "step" or "next"
>> when using bugpoint. The answer is no, but this is because bugpoint is
>> not a debugger like gdb. Bugpoint is a program that reduces testcases
>> that trigger bugs in LLVM passes.
>> Often times in LLVM development, some large LLVM bytecode file triggers
>> a bug in a set of LLVM passes. It is difficult to know what LLVM passes
>> are responsible for the failure or what part of the input is triggering
>> the problem. Bugpoint automates the process of narrowing down where a
>> bug is and what input is triggering it.
>> For more information, you can read about bugpoint at:
>> -- John T.
>>> Thank you.
>>> LLVM Developers mailing list
>>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
> LLVM Developers mailing list
> LLVMdev at cs.uiuc.edu http://llvm.cs.uiuc.edu
More information about the llvm-dev