From: Pawel Piech <pawel.piech@windriver.com>
To: gdb@sources.redhat.com
Subject: Re: Calling inferior functions and MI notification
Date: Mon, 31 Mar 2008 17:39:00 -0000 [thread overview]
Message-ID: <47F115EA.1060101@windriver.com> (raw)
In-Reply-To: <fsr2s9$tpr$1@ger.gmane.org>
Vladimir Prus wrote:
> Pawel Piech wrote:
>
>
>> It would be helpful if *running event included a "reason" field. IDE's
>> ususally track the command they just sent to determine the reason for
>> resume event, but as it's an out-of-band record there is a possibility
>> of a race condition which could break the IDE assumption.
>>
>
> Hello Pawel,
>
> can you clarify what the 'reason' field should contain? I think that in
> general, reporting the command that caused the run might be impossible.
>
>
Too bad, because that's what I had in mind.... Like I said, IDE's
including Eclipse usually solve this problem on their own, though the
solution is theoretically susceptible to a race condition in cases where
multiple interfaces are used to interact with GDB simultaneously.
Cheers,
Pawel
> - Volodya
>
>
>
next prev parent reply other threads:[~2008-03-31 16:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-27 19:02 Vladimir Prus
2008-03-31 13:00 ` Denis PILAT
2008-03-31 16:18 ` Daniel Jacobowitz
2008-03-31 16:49 ` Pawel Piech
2008-03-31 16:55 ` Vladimir Prus
2008-03-31 17:39 ` Pawel Piech [this message]
2008-03-31 22:05 ` Vladimir Prus
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=47F115EA.1060101@windriver.com \
--to=pawel.piech@windriver.com \
--cc=gdb@sources.redhat.com \
/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