public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Fernando Nasser <fnasser@cygnus.com>
To: tromey@redhat.com
Cc: Insight List <insight@sourceware.cygnus.com>
Subject: Re: question about breakpoints
Date: Mon, 04 Dec 2000 15:43:00 -0000	[thread overview]
Message-ID: <3A2C2C27.55E00F47@cygnus.com> (raw)
In-Reply-To: <87zoib3n80.fsf@creche.redhat.com>

Tom Tromey wrote:
> 
> I'd really like to access the `exp_string' and `addr_string' fields of
> gdb's `struct breakpoint'.  Currently the Tcl interface gives me no
> way to do that.
> 

Sorry Tom, I missed the fact that these two are not ever printed.
In this case a new function would be in order.  I also missed the fact
that before the CLI is converted, we cannot add info to this commands
without having them printed as well (something not difficult to fix but
that we haven't added because it would eventually become unnecessary).

I thought you were going to save/reinsert breakpoints based on the symbolic
information rather than in the addresses.  That has a better chance of surviving
between debugger invocation. In that case you could be able to reconstruct
a "linespec" from the print_one_breakpoint info (i.e., our gdb_get_breakpoint_info).

Regards,
Fernando

-- 
Fernando Nasser
Red Hat - Toronto                       E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9

  parent reply	other threads:[~2000-12-04 15:43 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-04 13:01 Tom Tromey
2000-12-04 13:49 ` Fernando Nasser
2000-12-04 14:51   ` Tom Tromey
2000-12-04 15:43 ` Fernando Nasser [this message]
2000-12-04 16:17   ` Tom Tromey
2000-12-05  5:54     ` Keith Seitz
2000-12-05  7:06       ` Fernando Nasser
2000-12-05  9:43         ` Tom Tromey
2000-12-05 10:06           ` Fernando Nasser
2000-12-05 12:17             ` Tom Tromey
2000-12-05  9:31       ` Tom Tromey
2000-12-05  9:40         ` Fernando Nasser

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=3A2C2C27.55E00F47@cygnus.com \
    --to=fnasser@cygnus.com \
    --cc=insight@sourceware.cygnus.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).