public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "forum at emblocks dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug corefiles/15974] Unsupported notification packets are causing errors (last of the nc_list is picked).
Date: Tue, 24 Sep 2013 10:27:00 -0000	[thread overview]
Message-ID: <bug-15974-4717-7Pxj2FEtFA@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15974-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15974

--- Comment #3 from Gerard Zagema <forum at emblocks dot org> ---
Yao,

You can commit yours, it's nicer.

Gerard.

BTW.

I need "simplex" notifications. That are asynchronous notifications which are
not acknowledged and are only signaling an event. It's a one shot packet from
remote to GDB without further information exchange. I couldn't find a way to
accomplish this in the current architecture so I added a field to the
notif_client that it shouldn't be Queued etc. The parser can handle it totally.

This is working very nice but I would prefer something that doesn't need all
kind of special patches. Is there something that I'm overlooking and is this
possible in the current setup?

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-09-24 10:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-23 14:14 [Bug corefiles/15974] New: " forum at emblocks dot org
2013-09-24  4:36 ` [Bug corefiles/15974] " forum at emblocks dot org
2013-09-24 10:12 ` qiyao at gcc dot gnu.org
2013-09-24 10:27 ` forum at emblocks dot org [this message]
2013-11-30  3:40 ` [Bug remote/15974] " qiyao at gcc dot gnu.org
2013-12-02  6:47 ` cvs-commit at gcc dot gnu.org
2013-12-02  6:55 ` qiyao at gcc dot gnu.org
2013-12-11  1:41 ` cvs-commit at gcc dot gnu.org
2013-12-13 16:52 ` cvs-commit at gcc dot gnu.org

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=bug-15974-4717-7Pxj2FEtFA@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).