search for: _somebody_

...r green, that would mean next to nothing as to what that > Dwarf would represent in the debugger(s). Well, having IR-level testing tells you next to nothing as to what your program would actually do when you compile and run it. But it seems to me that we have a huge pile of IR-level tests, so _somebody_ must think they are useful. :-) Sure, the acid test is whether the debugger does the right thing. I'm not saying debugger-based tests are worthless, I'm saying that _just_ having debugger-based tests is not _optimal_. DWARF-level testing would let you do things that debugger-based tests...

On 18 October 2012 21:36, Robinson, Paul <Paul.Robinson at am.sony.com> wrote: > Well, having IR-level testing tells you next to nothing as to what your > program would actually do when you compile and run it. But it seems > to me that we have a huge pile of IR-level tests, so _somebody_ must > think they are useful. :-) When creating Dwarf tests I did it at all levels: IR checking for metadata, ELF checking for Dwarf and GDB execution checking for correct behaviour. All that as LIT driven, so a "make check" would give me the results in a few seconds, with the benefi...

On 18 October 2012 02:53, Robinson, Paul <Paul.Robinson at am.sony.com> wrote: > I had a "quality suite" at a previous job; it was the result of many PY > of effort. It was also debugger-based, which is a mixed blessing; you > get a lot of DWARF-parsing code for free, but then you get a lot of > debugger bugs for free too! And you don't get to test the DWARF >

Rick Foos wrote: > The error we are getting is: > “Undefined Form Value: 25” > ... > DW_FORM_flag_present caused the problem. The old DW_FORM_flag works for us. I see this error from GDB 7.0 but GDB 7.2 is okay with it. Now you know as much as I do. :-) Eric Christopher wrote: > [in reply to what Renato Golin wrote:] > > With time, you might get to a point where Dwarf is a