> On Aug 30, 2016, at 7:33 AM, Howard Hellyer via lldb-dev
> wrote:
>
> "Ted Woodward" wrote on 26/08/2016 16:17:18:
>
> > That works fine for host debug, but not so much for embedded. On
> > Hexagon, we support 2 OS cases – standalone (which means no OS, or
> > an OS that lldb doesn’t know
"Ted Woodward" wrote on 26/08/2016 16:17:18:
> That works fine for host debug, but not so much for embedded. On
> Hexagon, we support 2 OS cases – standalone (which means no OS, or
> an OS that lldb doesn’t know anything about) and Linux. Both our
> standalone simulator and our Linux generate
M
To: Ted Woodward
Cc: Howard Hellyer ; Todd Fiala ;
LLDB
Subject: Re: [lldb-dev] Linux ELF header e_ident[EI_OSABI] value
It is ok for a core file to not pledge allegiance to an OS, it is ok for the OS
to be set to "*" or any OS. Linux core files are useless without the main
executabl
ad them together?
>
> --
> Qualcomm Innovation Center, Inc.
> The Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a
> Linux Foundation Collaborative Project
>
> From: Howard Hellyer [mailto:hhell...@uk.ibm.com]
> Sent: Friday, August 26, 2016 8:39 AM
&
ve Project
From: Howard Hellyer [mailto:hhell...@uk.ibm.com]
Sent: Friday, August 26, 2016 8:39 AM
To: Todd Fiala
Cc: LLDB ; Ted Woodward
Subject: Re: [lldb-dev] Linux ELF header e_ident[EI_OSABI] value
Todd Fiala mailto:todd.fi...@gmail.com> > wrote on
25/08/2016 20:42:31:
> FWI
Todd Fiala wrote on 25/08/2016 20:42:31:
> FWIW, I've taken a few whacks at getting Linux detected better over
> the last few years, and haven't yet found a reliable way to detect
> it from quite a few samples of cores from a number of different
> systems. We can spend more time looking into
FWIW, I've taken a few whacks at getting Linux detected better over the
last few years, and haven't yet found a reliable way to detect it from
quite a few samples of cores from a number of different systems. We can
spend more time looking into it, but that stone has been turned over
several times.
"Ted Woodward" wrote on 22/08/2016 21:03:02:
> We don't want to make ELFOSABI_NONE mean Linux. ELFOSABI_NONE is
> historically ELFOSABI_SYSV, and used by a lot of things. So not all
> core files identified as ELFOSABI_NONE are Linux.
I agree that other OS's may use it or have used it in the p
> I would change it so that the "os" doesn't get set to anything when
> it detects this in the core file. When an OS is not specified, the
> llvm::Triple will return OSUnknown as the enumeration value for the
> OS _and_ the llvm::StringRef value will return an empty string. This
> is known in LL
On 22 August 2016 at 16:03, Ted Woodward via lldb-dev
wrote:
>
> We don't want to make ELFOSABI_NONE mean Linux. ELFOSABI_NONE is historically
> ELFOSABI_SYSV, and used by a lot of things. So not all core files identified
> as ELFOSABI_NONE are Linux.
Indeed, and that's true for binaries and li
Hellyer
Cc: lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] Linux ELF header e_ident[EI_OSABI] value
> On Aug 22, 2016, at 6:00 AM, Howard Hellyer via lldb-dev
> wrote:
>
> I've been trying to understand why some Linux core files fail to load in
> lldb.
>
> The
> On Aug 22, 2016, at 6:00 AM, Howard Hellyer via lldb-dev
> wrote:
>
> I've been trying to understand why some Linux core files fail to load in
> lldb.
>
> The problem seems to be that in the ELF header Linux uses the ELFOSABI_NONE
> (0x0) value rather than ELFOSABIT_LINUX (0x3).If I eithe
I've been trying to understand why some Linux core files fail to load in
lldb.
The problem seems to be that in the ELF header Linux uses the
ELFOSABI_NONE (0x0) value rather than ELFOSABIT_LINUX (0x3).If I either
change the e_ident[EI_OSABI] byte to 0x3 in the header or the code in
ArchSpec.cp
13 matches
Mail list logo
