Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Matt Rice <ratmice@gmail.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>,
	gdb-patches@sourceware.org, 	Tom Tromey <tromey@redhat.com>,
	Sergio Durigan Junior <sergiodj@redhat.com>
Subject: Re: [PATCH 2/6] Introduce `pre_expanded sals'
Date: Tue, 12 Apr 2011 22:22:00 -0000	[thread overview]
Message-ID: <BANLkTinAdSTDymg1ykRnGrHm=oeONM9HUQ@mail.gmail.com> (raw)
In-Reply-To: <201104121430.24596.pedro@codesourcery.com>

On Tue, Apr 12, 2011 at 6:30 AM, Pedro Alves <pedro@codesourcery.com> wrote:
> Another argument,
> is that frontends and users using them aren't expecting that a single
> breakpoint is represented by more than one visual "point", circle next to
> the sources, or something like that.  Hitting F8 to toggle a breakpoint's
> enablement changing some other location source "point" enablement
> in the sources not currently visible seems to break some abstration
> to me.  I think such design change needs to consider all these
> issues (and be experimented with some frontend).

I think this "visual point" metaphor to some extent is already broken,
I more often than one might expect end up setting multiple breakpoints
on the same function
with different conditions and or commands.

could be as simple as a number inside the "visual point", and adding a
right-click 'breakpoint editor', thing to bring up another window.

to me, this seems like something which should be allowed, but not
something to surprise a user with.
thus, this leads me to ask, does this happen because it is the users
intent, or something else.


  parent reply	other threads:[~2011-04-12 22:22 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-04  3:08 Sergio Durigan Junior
2011-04-06 20:13 ` Tom Tromey
2011-04-12 11:18   ` Pedro Alves
2011-04-12 11:53     ` Jan Kratochvil
2011-04-12 13:30       ` Pedro Alves
2011-04-12 20:34         ` Tom Tromey
2011-04-12 22:22         ` Matt Rice [this message]
2011-04-13  9:53           ` Eli Zaretskii
2011-07-27 17:08         ` Tom Tromey
2011-07-29 20:36           ` Sergio Durigan Junior
2011-08-04 20:41             ` Tom Tromey
2011-08-05  3:41               ` Sergio Durigan Junior
2011-08-05 14:40                 ` Tom Tromey
2011-08-05 18:06                   ` Sergio Durigan Junior
2011-08-10 14:24           ` Tom Tromey
2011-05-03 16:09       ` Jerome Guitton
2011-05-03 18:17         ` Joel Brobecker
2011-04-12 20:26     ` Tom Tromey
2011-04-13  9:51       ` Eli Zaretskii
2011-04-13 19:20         ` Tom Tromey
2011-04-15 10:37           ` Eli Zaretskii
2011-04-18 18:37       ` Pedro Alves
2011-04-27 18:02         ` Jan Kratochvil
2011-04-29 20:42         ` Tom Tromey
2011-04-11 21:08 ` Jan Kratochvil

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='BANLkTinAdSTDymg1ykRnGrHm=oeONM9HUQ@mail.gmail.com' \
    --to=ratmice@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=jan.kratochvil@redhat.com \
    --cc=pedro@codesourcery.com \
    --cc=sergiodj@redhat.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