Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Nick Roberts <nickrob@snap.net.nz>
To: Joel Brobecker <brobecker@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [RFA/doco] document "set/show multiple-choice-auto-select"
Date: Fri, 25 Jan 2008 04:24:00 -0000	[thread overview]
Message-ID: <18329.25051.770437.318849@kahikatea.snap.net.nz> (raw)
In-Reply-To: <20080125025017.GG3979@adacore.com>

 > > I would guess that your proposed patch will overlap with one that I've
 > > recently submitted:
 > > 
 > > http://sourceware.org/ml/gdb-patches/2008-01/msg00421.html
 > 
 > I'm sorry - I am still jetlaged from my 36h trip and 12h time difference,
 > so I may be even more obtuse than usual ;-). IIUC, you are trying to
 > improve the situation in MI regarding multiple-location breakpoints,
 > right? Where is the overlapping? In the fact that you'll have to
 > modify the documentation in the same area? You'll have to forgive me,
 > I don't know the MI protocol apart from the general principles behind
 > it. This may also explain my questions...
 
The thread I refer to is about breakpoint menus and it follows (after some
delay) a bug report by Dodji Seketeli (nemiver).  Vladimir Prus has
suggested that we fix this in another way but I just thought I'd draw your
attention to it.  You don't need to know much about MI.  It just accepts
all the overloaded breakpoints when MI is the underlying interpreter.  Perhaps
I should have pointed here:

http://sourceware.org/ml/gdb/2008-01/msg00104.html

-- 
Nick                                           http://www.inet.net.nz/~nickrob


  reply	other threads:[~2008-01-25  4:13 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-24 21:36 Joel Brobecker
2008-01-24 23:50 ` Nick Roberts
2008-01-25  2:56   ` Joel Brobecker
2008-01-25  4:24     ` Nick Roberts [this message]
2008-01-25 10:52 ` Eli Zaretskii

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=18329.25051.770437.318849@kahikatea.snap.net.nz \
    --to=nickrob@snap.net.nz \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@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