Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Stan Shebs <stan@codesourcery.com>
Cc: gdb-patches@sourceware.org
Subject: Re: RFC: new struct breakpoint component cond_language...
Date: Tue, 11 May 2010 07:46:00 -0000	[thread overview]
Message-ID: <20100511074628.GF7479@adacore.com> (raw)
In-Reply-To: <4BE895C2.6090706@codesourcery.com>

> Tracepoints add an extra wrinkle to this concept - when connecting
> to a target that is currently running a trace, tracepoint conditions
> can be uploaded from the target, and in their original source form,
> and so have to be reparsed.  So to make this work in the
> multi-language case, it seems like the tracepoint download should
> include the language somehow.

I am not very familiar with tracepoints, but I think I see what
is happening (disconnecting GDB from the target?). It seems to me
that, indeed, tracepoints need to download and upload the condition
language as well. In particular:

> But then I wonder - when uploading a tracepoint, we receive both the
> computed address and the source form of that address, so in theory
> we can always deduce the correct language by working back from the
> tracepoint address.

I do not think so; At the time when the user declares the tracepoint
condition, I am assuming that we check the language mode, and that if
it is not auto, then we use the current_language as the condition
language, regardless of the language of the source. As a result,
the condition language cannot be determined from the tracepoint address.

-- 
Joel


  parent reply	other threads:[~2010-05-11  7:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-10 21:54 Joel Brobecker
2010-05-10 23:25 ` Stan Shebs
2010-05-10 23:28   ` Michael Snyder
2010-05-11  7:46   ` Joel Brobecker [this message]
2010-05-17 15:49 ` Tom Tromey

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=20100511074628.GF7479@adacore.com \
    --to=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=stan@codesourcery.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