[Lldb-commits] [lldb] r191996 - <rdar://problem/12042982>

[Thirumurthi, Ashok]

Hi Enrico,

I noticed a couple of failures exclusive to the "-C gcc" tests that I was able to bisect and reproduce with gcc 4.6.3 with your commit (see http://llvm.org/viewvc/llvm-project?revision=191996&view=revision).  These reproduce consistently on the public Linux buildbot, which uses gcc 4.6.2.  For instance, with the attached test log, I expected:

runCmd: frame variable strings
output: (string_vect) strings = size=3 {
    [0] = "goofy"
    [1] = "is"
    [2] = "smart"
}

The actual result is:

runCmd: frame variable strings
output: (string_vect) strings = size=3 {
    [0] = (_M_dataplus = std::basic_string<char, std::char_traits<char>, std::allocator<char, char>, char, std::char_traits<char>, std::allocator<char, char> >::_Alloc_hider @ 0x00000000016d2110)
    [1] = (_M_dataplus = std::basic_string<char, std::char_traits<char>, std::allocator<char, char>, char, std::char_traits<char>, std::allocator<char, char> >::_Alloc_hider @ 0x00000000016d2118)
    [2] = (_M_dataplus = std::basic_string<char, std::char_traits<char>, std::allocator<char, char>, char, std::char_traits<char>, std::allocator<char, char> >::_Alloc_hider @ 0x00000000016d2120)
}

Are you able to reproduce these regressions?  We should either fix this, revert the commit, or log a bugzilla and cross-reference an expectedFailureGcc with the test failures...

- Ashok
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Failure-x86_64-gcc-TestDataFormatterStdVector.StdVectorDataFormatterTestCase.test_with_dwarf_and_run_command.log
Type: application/octet-stream
Size: 9156 bytes
Desc: Failure-x86_64-gcc-TestDataFormatterStdVector.StdVectorDataFormatterTestCase.test_with_dwarf_and_run_command.log
URL: <http://lists.llvm.org/pipermail/lldb-commits/attachments/20131007/5a347029/attachment.obj>