[LLVMdev] bugpoint usage

[Seung Jae Lee]

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?
Thanks,

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:
>> Hello.
>> 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:
>
>http://llvm.org/docs/HowToSubmitABug.html
>http://llvm.org/docs/CommandGuide/html/bugpoint.html
>
>-- John T.
>
>> Thank you.
>> _______________________________________________
>> LLVM Developers mailing list
>> LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>> http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev
>>   
>
>_______________________________________________
>LLVM Developers mailing list
>LLVMdev at cs.uiuc.edu         http://llvm.cs.uiuc.edu
>http://lists.cs.uiuc.edu/mailman/listinfo/llvmdev