search for: end_prologu

...gt; I'm not sure what you mean here. I don't know what Rick has experienced, but I've seen that a DWARF problem can lead to an arbitrary number of GDB failures, none of which necessarily make it obvious what the problem is with the DWARF. For example, when tweaking the placement of the end_prologue flag in the line table made the "list" command break. Eh??? In that case at least I knew what I'd tweaked; coming on it cold, there's no way to know what's going on. --paulr

> > Take the log file, check out the suite, rerun a failing test, use dwarfdump > and llvm-dwarfdump, find the "bad" dwarf records produced by the compiler. > > All the eventual bugs are about dwarf records, and a gdb testsuite test to > duplicate. > That's not necessarily the case. > A bad/confused dwarf record fails multiple tests without a way to map a

On 10/18/2012 01:39 PM, David Blaikie wrote: > On Thu, Oct 18, 2012 at 11:19 AM, Rick Foos<rfoos at codeaurora.org> wrote: >> On 10/18/2012 10:36 AM, David Blaikie wrote: >>> On Thu, Oct 18, 2012 at 12:48 AM, Renato Golin<rengolin at systemcall.org> >>> wrote: >>>> On 18 October 2012 05:11, Rick Foos<rfoos at codeaurora.org> wrote: