On Mon, Nov 16, 2015 at 11:28 PM, Todd Fiala wrote:
>
>
> On Fri, Nov 13, 2015 at 9:02 AM, Todd Fiala wrote:
>
>> Hi all,
>>
>> I'd like to do a few things with our swig generation and handling:
>>
>> * Create a maintainer-mode style setup where the swig Python bindings are
>> generated and chec
On Fri, Nov 13, 2015 at 9:02 AM, Todd Fiala wrote:
> Hi all,
>
> I'd like to do a few things with our swig generation and handling:
>
> * Create a maintainer-mode style setup where the swig Python bindings are
> generated and checked into the repo (I'll call it the static python
> binding).
>
> T
lldb has "target stop-hook"s that you can use to add LLDB command-line commands
to react to any sort of stop. The intent is to also allow Python stop hooks,
then you could switch on the thread's stop reason and do signal specific stuff
for a signal stop. But nobody has gotten around to adding
You are right, it does work - sorry for false alarm.
> From: lab...@google.com
> Date: Mon, 16 Nov 2015 11:26:10 +
> Subject: Re: [lldb-dev] Is there a way to inspect signaled stack?
> To: eugen...@hotmail.com
> CC: lldb-dev@lists.llvm.org
>
> Hi Eugene,
>
> the libc signal trampoline should
Thanks for the heads-up Mikhail.
Ravi,
this looks like your code. Could you take a look at this?
pl
On 16 November 2015 at 16:24, Mikhail Filimonov via lldb-dev
wrote:
> Hi guys and thank you for the excellent community project!
>
>
>
> Recently I’ve stumbled on a pesky, but trivial Invalid i
Hi guys and thank you for the excellent community project!
Recently I've stumbled on a pesky, but trivial Invalid iterator dereference bug
in SymbolContext and TypeMap implementations at revisions
https://github.com/llvm-mirror/lldb/blob/e528da256d14ecac7df858462b44dca931879509/source/Symbol/Symb
Hi Eugene,
the libc signal trampoline should have .eh_frame unwind info (I am
assuming this is x86_64 btw), and last time I looked at it, it seemed
that it should be able to handle sigaltstack(). However, I have never
tested this, so it's quite possible there is still some bug hidden
there. Could
I believe there is no such thing at the moment. It might be
interesting to add one though, to enable "conditional" signal
handling. E.g., when an application handles it's own SIGSEGVs, and you
want to pass those quietly, but you want to stop for real problems
(for some definition of "real").
pl
O
https://llvm.org/bugs/show_bug.cgi?id=23560
abhiinnit...@gmail.com changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
