Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: gdb-patches@sourceware.org
Subject: RFC: skip_inline_frames failed assertion resuming from breakpoint on LynxOS
Date: Thu, 20 Nov 2014 05:11:00 -0000	[thread overview]
Message-ID: <20141120051109.GR5774@adacore.com> (raw)

Hello,

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).

Thank you!
-- 
Joel


             reply	other threads:[~2014-11-20  5:11 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-20  5:11 Joel Brobecker [this message]
2014-11-20  5:12 ` Joel Brobecker
2014-11-20  9:55   ` Pedro Alves
2014-11-20 17:11     ` Joel Brobecker
2014-11-21 10:43       ` Pedro Alves
2014-12-13 15:46         ` Joel Brobecker
2014-12-15 13:11           ` Pedro Alves
2014-12-15 14:58             ` Joel Brobecker
2014-12-15 16:01               ` Pedro Alves

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20141120051109.GR5774@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox