From: Jim Ingham Date: Wed, 7 Nov 2012 01:52:04 +0000 (+0000) Subject: When we were calculating the max byte size of ONE instruction to handle something... X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=d073fe4e5b79557d4e8662db1a7d9465dc19fdb3;p=platform%2Fupstream%2Fllvm.git When we were calculating the max byte size of ONE instruction to handle something like x/9i we actually calculated the size of 9 instructions. Then we multiplied it by the count again to get the total amount we should fetch, so we thought 9 x86_64 instructions took over 1K to fetch... llvm-svn: 167520 --- diff --git a/lldb/source/Commands/CommandObjectMemory.cpp b/lldb/source/Commands/CommandObjectMemory.cpp index 5360e71..99a3593 100644 --- a/lldb/source/Commands/CommandObjectMemory.cpp +++ b/lldb/source/Commands/CommandObjectMemory.cpp @@ -148,7 +148,7 @@ public: case eFormatInstruction: if (count_option_set) - byte_size_value = target->GetArchitecture().GetMaximumOpcodeByteSize() * format_options.GetCountValue().GetCurrentValue(); + byte_size_value = target->GetArchitecture().GetMaximumOpcodeByteSize(); m_num_per_line = 1; break;