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: [RFA] info (break|watch|trace), use get_number_or_range

From: Michael Snyder <msnyder at vmware dot com>
To: Pedro Alves <pedro at codesourcery dot com>
Cc: "msnyder at sonic dot net" <msnyder at sonic dot net>, "gdb-patches at sourceware dot org" <gdb-patches at sourceware dot org>
Date: Mon, 21 Feb 2011 11:55:21 -0800
Subject: Re: [RFA] info (break|watch|trace), use get_number_or_range
References: <9c90ed265767e17ab56f1f865d10999d.squirrel@webmail.sonic.net> <201102202129.11630.pedro@codesourcery.com>

Pedro Alves wrote:

On Saturday 19 February 2011 18:01:44, msnyder@sonic.net wrote:

This will break printing internal breakpoints, which are negative.
AFAIK, "info break" never supported printing internal breakpoints.
That's what "maint info break" is for.


Sorry, I misread and though you were changing breakpoint_1, which
is the backend for "info break", "maint info break", etc.

Doesn't this patch have the same problem I pointed out with
"info threads 1-100", in that you'll print the header once
for each breakpoint in the range?

<sigh>, yes. I'll withdraw this one and try a different approach.

References:
- Re: [RFA] info (break|watch|trace), use get_number_or_range
  - From: msnyder
- Re: [RFA] info (break|watch|trace), use get_number_or_range
  - From: Pedro Alves

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