> that comes out of python
that comes out of swig, rather (i.e. the binding generation output).
On Tue, Nov 17, 2015 at 8:03 PM, Todd Fiala wrote:
> Nothing concrete at the moment; however, it could be interesting to look
> at the clang community and see what could be done for llvm-based langua
Nothing concrete at the moment; however, it could be interesting to look at
the clang community and see what could be done for llvm-based language
implementations. The angle that I think would be interesting would be if
we can generate bindings more effectively based on the in-depth
understanding
Stepping one step back further in the thread ...
On Wed, Nov 18, 2015 at 8:35 AM, Zachary Turner via lldb-commits <
lldb-comm...@lists.llvm.org> wrote:
> Moving this back over to the list since I'm sure others have some input
> here. Also +lldb-dev since it has more visibility than lldb-commits.
Moving this back over to the list since I'm sure others have some input
here. Also +lldb-dev since it has more visibility than lldb-commits.
On Tue, Nov 17, 2015 at 11:25 AM Zachary Turner wrote:
> On Tue, Nov 17, 2015 at 8:18 AM Todd Fiala wrote:
>
>> Breaking out the binding generation into
https://llvm.org/bugs/show_bug.cgi?id=25562
Bug ID: 25562
Summary: Some failing tests are being reported as passes
Product: lldb
Version: unspecified
Hardware: PC
OS: Windows NT
Status: NEW
Severity: norma
Ok I see what you're saying. I was trying to use the next symbol address
as a delimeter but I realised they were not in order. It is a PECOFF
binary that I'm debugging so I will take a look at the code suggested
below.
Thanks ,
Que
On 17/11/15 18:07, Greg Clayton wrote:
It sounds like the
It sounds like the symbols in the symbol table don't have valid sizes when they
really should. What kind of executable are you debugging? A PECOFF file? If so,
you should take a look at and fix the code in:
Symtab *
ObjectFilePECOFF::GetSymtab()
What we do for mach-o is to parse the symbol tabl
Hi,
I'm building an application on windows using the python api. I need to
be able to access a code symbols instructions but when I launch the
process the symbol has no instructions. I can manually read the symbols
address space but the symbol also has no end_addr set which makes it
difficult
Hello,
Yeah you are right Mikhail, thanks for pointing it out, I
must ask, is there any bug already logged for this issue ?
Ravi
On Mon, Nov 16, 2015 at 5:24 PM, Mikhail Filimonov via lldb-dev <
lldb-dev@lists.llvm.org> wrote:
> Hi guys and thank you for the excellent community
Hello, Ravi - you're welcome. I haven't filled a bug in lldb bug tracker, just
mailed to dev list.
Mikhail
-Original Message-
From: Addepally, Ravitheja [mailto:ravitheja.addepa...@intel.com]
Sent: Tuesday, November 17, 2015 12:34 PM
To: Pavel Labath ; Mikhail Filimonov
Cc: lldb-dev@l
10 matches
Mail list logo
