22:29
> To: Bhushan Attarde
> Cc: lldb-dev@lists.llvm.org
> Subject: Re: [lldb-dev] llvm assertion while evaluating expressions for MIPS
> on Linux
>
> What happens if we go with "_$" as our private prefix? Or maybe "lldb$"?
> Would this avoid the issue and f
b-dev@lists.llvm.org
Subject: Re: [lldb-dev] llvm assertion while evaluating expressions for MIPS on
Linux
What happens if we go with "_$" as our private prefix? Or maybe "lldb$"? Would
this avoid the issue and fix things for MIPS? I would rather us have a
consistent private naming
k removing C Language linkage from function
> "$__lldb_valid_pointer_check" can be a solution? or do you have a better
> solution to this issue?
>
> Regards,
> Bhushan
>
>
> -Original Message-
> From: Greg Clayton [mailto:gclay...@apple.com]
> Sent:
inal Message-
From: Greg Clayton [mailto:gclay...@apple.com]
Sent: 20 October 2015 23:56
To: Greg Clayton
Cc: Bhushan Attarde; lldb-dev@lists.llvm.org
Subject: Re: [lldb-dev] llvm assertion while evaluating expressions for MIPS on
Linux
My guess is that there is a different temporary symbol for
My guess is that there is a different temporary symbol for differing
architectures and possibly depending on which file format (mach-o or ELF) you
are targeting. MIPS probably happens to use '$'. I know mach-o files use "L" as
the temporary symbol prefix, ELF tends to use '.'. Not sure where thi
What is this not happening on any other architecture? Is the "$" special for
MIPS and not for other architectures? We really don't want to remove the '$' as
we want the symbol to be unique. The '$' symbol is fine for all x86/x86_64/arm
and arm64 variants...
Greg
> On Oct 19, 2015, at 11:30 PM
Hi,
I am facing issue (llvm assertion) in evaluating expressions for MIPS on Linux.
(lldb) p fooptr(a,b)
lldb: /home/battarde/git/llvm/lib/MC/ELFObjectWriter.cpp:791: void
{anonymous}::ELFObjectWriter::computeSymbolTable(llvm::MCAssembler&, const
llvm::MCAsmLayout&, const SectionIndexMapTy&, co
