Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Vladimir Prus <vladimir@codesourcery.com>
To: Mircea Gherzan <mgherzan@gmail.com>
Cc: Marc Khouzam <marc.khouzam@ericsson.com>,
	'Mircea Gherzan'	<mircea.gherzan@intel.com>,
	"'tromey@redhat.com'" <tromey@redhat.com>,
	"'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [RFC] Fix the MI result of -break-insert with multiple locations
Date: Tue, 29 Jan 2013 20:36:00 -0000	[thread overview]
Message-ID: <510832AA.7050502@codesourcery.com> (raw)
In-Reply-To: <510822D1.1030103@gmail.com>

On 29.01.2013 23:28, Mircea Gherzan wrote:
> Am 29.01.2013 17:26, schrieb Vladimir Prus:
>> I think it would help to see complete output, without ellipsis.
>
> I provided the full output of -break-insert with an overloaded function
> in a previous e-mail [1].

I did read that, but don't see the output after your patch.

>
>> (And when we agree that the proposed output is good, the patch would
>> need testsuite changes to be accepted)
>
> AFAICT the MI test suite does not currently contain any tests for the
> multiple location case. So I guess you want a new test in mi-break.exp,
> right?

Yes, sorry for being unclear.

-- 
Vladimir Prus
CodeSourcery / Mentor Graphics
http://www.mentor.com/embedded-software/


  reply	other threads:[~2013-01-29 20:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29 14:36 Mircea Gherzan
2013-01-29 15:39 ` Marc Khouzam
2013-01-29 15:52   ` Mircea Gherzan
2013-01-29 16:04     ` Marc Khouzam
2013-01-29 16:26       ` Vladimir Prus
2013-01-29 19:28         ` Mircea Gherzan
2013-01-29 20:36           ` Vladimir Prus [this message]
2013-01-29 20:55             ` Mircea Gherzan
2013-01-29 19:45 ` André Pönitz
2013-01-29 20:42   ` Marc Khouzam
2013-01-29 22:14     ` André Pönitz
2013-01-30 16:27       ` 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=510832AA.7050502@codesourcery.com \
    --to=vladimir@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=marc.khouzam@ericsson.com \
    --cc=mgherzan@gmail.com \
    --cc=mircea.gherzan@intel.com \
    --cc=tromey@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