Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Doug Evans <dje@google.com>
Cc: gerhard.gappmeier@ascolab.com, gdb-patches@sourceware.org
Subject: Re: New feature "source-id"
Date: Sat, 15 Mar 2014 20:06:00 -0000	[thread overview]
Message-ID: <83siqjb50u.fsf@gnu.org> (raw)
In-Reply-To: <CADPb22RsRdFvr09HC_zj_tvBVLEScC6UzgNs=UCjpf3zWCt_gQ@mail.gmail.com>

> Date: Sat, 15 Mar 2014 10:32:12 -0700
> From: Doug Evans <dje@google.com>
> Cc: gdb-patches <gdb-patches@sourceware.org>
> 
> But IMO the fetching of source must go through the Extension Language API.
> See gdb/extension*.[ch].
> I.e., don't do the popen in gdb.  Just call out to the extension
> language via the API (e.g, Python), passing it the necessary
> parameters.

That would mean the feature will be unavailable in a GDB compiled
without Python and Guile.


  reply	other threads:[~2014-03-15 20:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-15 10:49 Gerhard Gappmeier
2014-03-15 17:32 ` Doug Evans
2014-03-15 20:06   ` Eli Zaretskii [this message]
2014-03-16  2:34     ` Doug Evans
2014-03-16  9:43       ` Gerhard Gappmeier
2014-03-16 16:22       ` Doug Evans
2014-03-16 16:34         ` Eli Zaretskii
2014-03-17  8:49         ` Gerhard Gappmeier
2014-03-17 12:25           ` Matt Rice
2014-03-17 19:01             ` Gerhard Gappmeier
2014-03-18  0:25               ` Doug Evans
2014-03-18  0:48                 ` Bruce Dawson
2014-03-18  1:39                   ` Doug Evans
2014-03-18 17:44                     ` Bruce Dawson
2014-03-18 17:57                       ` Doug Evans
2014-03-18 13:22 ` Mark Wielaard
2014-03-18 14:00   ` Gerhard Gappmeier
2014-03-18 15:03     ` Mark Wielaard
2014-03-18 16:40       ` Gerhard Gappmeier
2014-03-18 17:56         ` Bruce Dawson
2014-05-21 19:30           ` Tom Tromey
2014-05-21 20:42             ` Bruce Dawson

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=83siqjb50u.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dje@google.com \
    --cc=gdb-patches@sourceware.org \
    --cc=gerhard.gappmeier@ascolab.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