search for: llgdb

...ous tests to measure how much debuginfo was destroyed by different LLVM passes. As far as I understand it, the existing debuginfo-tests [5] contain debugger commands that are fed into a debugger, and the debugger output is FileCheck'd. This works directly for gdb, and there's a thin layer (llgdb.py) for driving lldb, but windows-based cdb has a very different input language and has its own set of tests. An obvious win would be unifying these, which is something Dexter could be adapted to do. I'm sure most agree, it would be better to declare the expected behaviour in some language and...

...rom input source program +# comments in a script. A debugger is used to load the executable file +# and run the script generated from source program comments. Finally, +# the debugger output is checked, using FileCheck, to validate +# debugging information. +# +# On Darwin the default is to use the llgdb.py wrapper script which +# translates gdb commands into their lldb equivalents. + +use File::Basename; +use Config; +use Cwd; + +my $testcase_file = $ARGV[0]; +my $executable_file = $ARGV[1]; + +my $input_filename = basename $testcase_file; +my $output_dir = dirname $executable_file; + +my $debugge...

...ipt. A debugger is used to load the executable file >> +# and run the script generated from source program comments. Finally, >> +# the debugger output is checked, using FileCheck, to validate >> +# debugging information. >> +# >> +# On Darwin the default is to use the llgdb.py wrapper script which >> +# translates gdb commands into their lldb equivalents. >> + >> +use File::Basename; >> +use Config; >> +use Cwd; >> + >> +my $testcase_file = $ARGV[0]; >> +my $executable_file = $ARGV[1]; >> + >> +my $input_file...

...+# comments in a script. A debugger is used to load the executable file > +# and run the script generated from source program comments. Finally, > +# the debugger output is checked, using FileCheck, to validate > +# debugging information. > +# > +# On Darwin the default is to use the llgdb.py wrapper script which > +# translates gdb commands into their lldb equivalents. > + > +use File::Basename; > +use Config; > +use Cwd; > + > +my $testcase_file = $ARGV[0]; > +my $executable_file = $ARGV[1]; > + > +my $input_filename = basename $testcase_file; > +my...

...>>>>> >>>>> >>>>>> >>>>> Wasn't quite fixed, but it got a lot further this time. This >>>>>> time there was still an issue in the test_debuginfo.pl script >>>>>> regarding a hardcoded path to the llgdb.py script. I think I never >>>>>> encountered this locally because this codepath only happens on Darwin, and >>>>>> I was testing on Linux. >>>>>> >>>>> >>>>>> >>>>> (As an aside, ugh... Perl...)...

...ommand line. In a previous discussion [https://reviews.llvm.org/D54187], the idea of using Dexter to drive the debuginfo-tests was raised as a solution to adding cdb support without needing to maintain an entirely separate suite of tests (as is currently the case). It can also replace the existing llgdb layer, which provides a frontend for driving tests with GDB and LLDB; the upshot being that each test can be written once and then run with any desired debugger. The Dexter test commands are also more concise than the equivalent set of debugger commands: where the existing tests require 3 separate...

...drian > On Nov 10, 2017, at 3:14 PM, Zachary Turner <zturner at google.com> wrote: > > Wasn't quite fixed, but it got a lot further this time. This time there was still an issue in the test_debuginfo.pl <http://test_debuginfo.pl/> script regarding a hardcoded path to the llgdb.py script. I think I never encountered this locally because this codepath only happens on Darwin, and I was testing on Linux. > > (As an aside, ugh... Perl...) > > Regardless, this should be fixed in r317949, and hopefully that's the last of the issues. I have to run for a coupl...

> On Nov 10, 2017, at 2:50 PM, Zachary Turner <zturner at google.com> wrote: > > I checked in a fix for that already, sorry for the trouble. I’m waiting for it to cycle awesome. Thanks! -- adrian > On Fri, Nov 10, 2017 at 2:49 PM Adrian Prantl <aprantl at apple.com <mailto:aprantl at apple.com>> wrote: > It looks like this broke green dragon: > >

...t; >> >> On Nov 10, 2017, at 3:14 PM, Zachary Turner <zturner at google.com> wrote: >> >> Wasn't quite fixed, but it got a lot further this time. This time there >> was still an issue in the test_debuginfo.pl script regarding a hardcoded >> path to the llgdb.py script. I think I never encountered this locally >> because this codepath only happens on Darwin, and I was testing on Linux. >> >> (As an aside, ugh... Perl...) >> >> Regardless, this should be fixed in r317949, and hopefully that's the >> last of the is...

...er <zturner at google.com <mailto:zturner at google.com>> wrote: >>> >>> Wasn't quite fixed, but it got a lot further this time. This time there was still an issue in the test_debuginfo.pl <http://test_debuginfo.pl/> script regarding a hardcoded path to the llgdb.py script. I think I never encountered this locally because this codepath only happens on Darwin, and I was testing on Linux. >>> >>> (As an aside, ugh... Perl...) >>> >>> Regardless, this should be fixed in r317949, and hopefully that's the last of the is...

...turner at google.com <mailto:zturner at google.com>> wrote: >>>> >>>> Wasn't quite fixed, but it got a lot further this time. This time there was still an issue in the test_debuginfo.pl <http://test_debuginfo.pl/> script regarding a hardcoded path to the llgdb.py script. I think I never encountered this locally because this codepath only happens on Darwin, and I was testing on Linux. >>>> >>>> (As an aside, ugh... Perl...) >>>> >>>> Regardless, this should be fixed in r317949, and hopefully that's th...

...2017, at 3:14 PM, Zachary Turner <zturner at google.com> > wrote: > >>>>> > >>>>> Wasn't quite fixed, but it got a lot further this time. This time > there was still an issue in the test_debuginfo.pl script regarding a > hardcoded path to the llgdb.py script. I think I never encountered this > locally because this codepath only happens on Darwin, and I was testing on > Linux. > >>>>> > >>>>> (As an aside, ugh... Perl...) > >>>>> > >>>>> Regardless, this should be f...

...achary Turner <zturner at google.com> >> wrote: >> >>>>> >> >>>>> Wasn't quite fixed, but it got a lot further this time. This time >> there was still an issue in the test_debuginfo.pl script regarding a >> hardcoded path to the llgdb.py script. I think I never encountered this >> locally because this codepath only happens on Darwin, and I was testing on >> Linux. >> >>>>> >> >>>>> (As an aside, ugh... Perl...) >> >>>>> >> >>>>> Rega...

...gt; >>>> wrote: >>>> >>>>> >>>> >>>>> Wasn't quite fixed, but it got a lot further this time. This >>>> time there was still an issue in the test_debuginfo.pl script >>>> regarding a hardcoded path to the llgdb.py script. I think I never >>>> encountered this locally because this codepath only happens on Darwin, and >>>> I was testing on Linux. >>>> >>>>> >>>> >>>>> (As an aside, ugh... Perl...) >>>> >>>&gt...