This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: [2/2] RFC: let "commands" affect multiple breakpoints

From: Tom Tromey <tromey at redhat dot com>
To: Pedro Alves <pedro at codesourcery dot com>
Cc: gdb-patches at sourceware dot org
Date: Tue, 30 Mar 2010 14:42:42 -0600
Subject: Re: [2/2] RFC: let "commands" affect multiple breakpoints
References: <m31vfsltl7.fsf@fleche.redhat.com> <m3bpefpsxu.fsf@fleche.redhat.com> <m3vdclh0vv.fsf@fleche.redhat.com> <201003251709.32951.pedro@codesourcery.com>
Reply-to: tromey at redhat dot com

>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:

Pedro> I have a suggestion for this, in form of a patch.  How
Pedro> about we just print the breakpoint range?  

It makes sense to me.

I think I didn't do this because I thought it would look weird if the
user entered an invalid range specifier.  But on reflection I'm not
concerned about that.

Pedro> WDYT?

It looks reasonable to me, though be sure to incorporate the subsequent
bug fix:

2010-03-26  Tom Tromey  <tromey@redhat.com>

	* breakpoint.c (commands_command_1): Duplicate 'arg'.

Tom

References:
- [2/2] RFC: let "commands" affect multiple breakpoints
  - From: Tom Tromey
- Re: [2/2] RFC: let "commands" affect multiple breakpoints
  - From: Tom Tromey
- Re: [2/2] RFC: let "commands" affect multiple breakpoints
  - From: Tom Tromey
- Re: [2/2] RFC: let "commands" affect multiple breakpoints
  - From: Pedro Alves

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]