Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [WIP] TI msp430 CIO support
Date: Fri, 17 May 2013 06:36:00 -0000	[thread overview]
Message-ID: <20130517063603.GF4017@adacore.com> (raw)
In-Reply-To: <20130516212358.23f3bcdb@mesquite.lan>

> It may be that this is considered to be (barely) acceptable behavior
> for dprintf.  Even if this is acceptable for dprintf, it is completely
> unacceptable for the CIO implementation.  It makes no sense whatsoever
> to turn a "next" into a "continue" when attempting to step over a
> statement which performs I/O.

Agreed. Having dprintf with limitations is probably better than
no dprintf at all, but that is a very very serious limitation, IMO.

> In order for this work to go into the GDB sources, the use of the
> shared library machinery needs to be removed and replaced with some
> other kind of breakpoint machinery which still provides correct
> behavior.   This same mechanism could be used to improve dprintf
> behavior as well.

Agreed again. I think this option has been delayed and delayed because
it might be hairy to implement right (messing with handle_inferior_event).

-- 
Joel


  reply	other threads:[~2013-05-17  6:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-17  4:24 Kevin Buettner
2013-05-17  6:36 ` Joel Brobecker [this message]
2013-05-17  8:43 ` Yao Qi
2013-05-17 21:44 ` Mike Frysinger
2013-05-17 23:10   ` Kevin Buettner
2013-05-20 14:39 ` Tom Tromey
2013-05-21 16:00   ` Kevin Buettner

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=20130517063603.GF4017@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kevinb@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