From: Marc Khouzam <marc.khouzam@ericsson.com>
To: 'Pedro Alves' <palves@redhat.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: RE: [PATCH] PR breakpoints/15697: Remove =breakpoint-modified when hitting dprintf
Date: Tue, 29 Apr 2014 17:48:00 -0000 [thread overview]
Message-ID: <E59706EF8DB1D147B15BECA3322E4BDC1C60EF02@eusaamb103.ericsson.se> (raw)
In-Reply-To: <535FDAB3.7010601@redhat.com>
> -----Original Message-----
> From: Pedro Alves [mailto:palves@redhat.com]
> Sent: Tuesday, April 29, 2014 1:01 PM
> To: Marc Khouzam
> Cc: gdb-patches@sourceware.org
> Subject: Re: [PATCH] PR breakpoints/15697: Remove =breakpoint-modified
> when hitting dprintf
[Bunch of very valid concerns]
> Related, I'm not sure we should filter the
> observer_notify_breakpoint_modified call -- it would seem better if
> observers are notified, and the its MI that filters out those modifications that
> it isn't interested in.
> E.g., could TUI be interested in still receiving the nofications?
Something to think about. Simon made the same comment off-line.
> I don't have answers to the above, but I think these issues all need to be
> considered, and whatever resolutions we end up with need to be cast as
> comments in the code and manual.
Thanks Pedro, you are bringing up valid (and tricky :-)) points. I'll look into them
and see if I can come up with equally valid solutions.
Marc
next prev parent reply other threads:[~2014-04-29 17:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 20:24 Marc Khouzam
2014-04-28 22:06 ` Doug Evans
2014-04-29 17:18 ` Pedro Alves
2014-04-29 17:48 ` Marc Khouzam [this message]
2014-05-20 19:45 ` Marc Khouzam
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=E59706EF8DB1D147B15BECA3322E4BDC1C60EF02@eusaamb103.ericsson.se \
--to=marc.khouzam@ericsson.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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