RFC: skip_inline_frames failed assertion resuming from breakpoint on LynxOS

[Joel Brobecker]

[Fixing ENOPATCH... sigh.]
> I was wondering what you guys would think of a patch like this.
> I am a bit uncertain, because I don't understand everything
> that is happening - and the problem is that this is happening
> with a fairly massive and complex program that I don't have access
> to, on a system that is also fairly opaque. When I'm lucky, getting
> answers is only very hard.
> 
> I am still trying to reproduce the problem locally in order to
> find out more, but I couldn't understand why, in principle,
> one thread couldn't receive multiple notifications during
> the same single-step if the system decides to queue up signals?
> If that were the case, wouldn't the attached patch make sense?
> (currently untested against the program that triggered the issue,
> as I think I understand how inline-frame works, and what it does,
> but I am not sure I get it all).

Thanks again!
-- 
Joel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-skip_inline_frames-failed-assertion-resuming-from-br.patch
Type: text/x-diff
Size: 4705 bytes
Desc: not available
URL: <http://sourceware.org/pipermail/gdb-patches/attachments/20141120/aa92dcc2/attachment.bin>