[lldb-dev] [Bug 37950] New: ExecutionContext::GetByteOrder() always returns endian::InlHostByteOrder()

[via lldb-dev]

https://bugs.llvm.org/show_bug.cgi?id=37950

            Bug ID: 37950
           Summary: ExecutionContext::GetByteOrder() always returns
                    endian::InlHostByteOrder()
           Product: lldb
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P
         Component: All Bugs
          Assignee: lldb-dev at lists.llvm.org
          Reporter: ramana.venkat83 at gmail.com
                CC: llvm-bugs at lists.llvm.org

Created attachment 20471
  --> https://bugs.llvm.org/attachment.cgi?id=20471&action=edit
Patch

lldb::ByteOrder ExecutionContext::GetByteOrder() const {
  if (m_target_sp && m_target_sp->GetArchitecture().IsValid())
    m_target_sp->GetArchitecture().GetByteOrder();
  if (m_process_sp)
    m_process_sp->GetByteOrder();
  return endian::InlHostByteOrder();
}

As can be seen from the above piece of code, the byte order returned is always
endian::InlHostByteOrder(), which is not wrong.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.llvm.org/pipermail/lldb-dev/attachments/20180627/d44b1c6a/attachment.html>