Re: [lldb-dev] negative in stop reason

2017-11-20 Thread Jim Ingham via lldb-dev
The breakpoint hit count is not increasing, which makes it look like we aren’t managing to do the job of stepping past the breakpoint. That requires restoring the breakpoint instruction, setting the processor to single-step, running just the thread that hit the breakpoint, then reinserting

Re: [lldb-dev] Unifying ctor+Clear() inits into in-class initializers?

2017-11-20 Thread Zachary Turner via lldb-dev
+1, this pattern looks like asking for UB On Mon, Nov 20, 2017 at 11:57 AM Leonard Mosescu via lldb-dev < lldb-dev@lists.llvm.org> wrote: > void Clear() { >> this->~ClassName(); >> new (this) ClassName(); >> } > > > My 2c: this is clever, but not without

Re: [lldb-dev] Unifying ctor+Clear() inits into in-class initializers?

2017-11-20 Thread Leonard Mosescu via lldb-dev
> > void Clear() { > this->~ClassName(); > new (this) ClassName(); > } My 2c: this is clever, but not without downsides: 1. It may do more than intended (it will destroy all members / bases) 2. It forces construction and 'reset' to be exactly the same, which