Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: "Pierre Muller" <muller@ics.u-strasbg.fr>
To: "'Vladimir Prus'" <ghost@cs.msu.su>, 	<gdb-patches@sources.redhat.com>
Subject: RE: [RFA] Use vector for varobj_list_children interface.
Date: Wed, 30 Jan 2008 08:48:00 -0000	[thread overview]
Message-ID: <000101c8631b$aa13cbb0$fe3b6310$@u-strasbg.fr> (raw)
In-Reply-To: <fnpcjr$tt5$1@ger.gmane.org>



> -----Original Message-----
> From: gdb-patches-owner@sourceware.org [mailto:gdb-patches-
> owner@sourceware.org] On Behalf Of Vladimir Prus
> Sent: Wednesday, January 30, 2008 9:31 AM
> To: gdb-patches@sources.redhat.com
> Subject: RE: [RFA] Use vector for varobj_list_children interface.
> 
> Pierre Muller wrote:
> 
> > Volodya,
> >
> >   I suspect that your commit broke
> > gdbtk:
> 
> Hmm. What is gdbtk and why is it a part of gdb checkout?
I think it is the part used by insight
just do a cvs up -d at src/gdb level
and you will get the src/gdb/gdbtk directory if you don't have it.

 To compile gdbtk,I think that you need
to configure at src level with --enable-libgui 
but you might need some other directories.
  Otherwise just look into gdbtk subdirectory for
the functions that you modified and adapt the code.
  If you send it back to the list, I can test it and check it in 
as obvious fix on your behalf.

Daniel, is that OK?

Pierre Muller



  reply	other threads:[~2008-01-30  8:40 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17 14:56 Vladimir Prus
2008-01-29 21:54 ` Daniel Jacobowitz
2008-01-30  7:22   ` Vladimir Prus
2008-01-30  8:31     ` Pierre Muller
2008-01-30  8:40       ` Vladimir Prus
2008-01-30  8:48         ` Pierre Muller [this message]
2008-01-30 13:52           ` Daniel Jacobowitz
2008-01-30 13:57             ` Vladimir Prus
2008-01-30 14:05               ` Daniel Jacobowitz
2008-01-30 14:17                 ` Daniel Jacobowitz
2008-01-30 15:09                 ` Vladimir Prus

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='000101c8631b$aa13cbb0$fe3b6310$@u-strasbg.fr' \
    --to=muller@ics.u-strasbg.fr \
    --cc=gdb-patches@sources.redhat.com \
    --cc=ghost@cs.msu.su \
    /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