public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Keith Seitz <keiths@redhat.com>
To: Roland Schwingel <roland@onevision.com>
Cc: insight@sourceware.org
Subject: Re: Make insight compileable again
Date: Wed, 08 Aug 2012 14:18:00 -0000	[thread overview]
Message-ID: <5022750D.4050207@redhat.com> (raw)
In-Reply-To: <50226F7A.8080206@onevision.com>

On 08/08/2012 06:54 AM, Roland Schwingel wrote:

> Due to some changes some weeks ago in gdb current insight did no
> longer compile. I committed a small patch to fix this.

I've been remiss keeping up on this. I haven't actually attempted to 
compile insight in several weeks. I've been too busy debugging stuff!

>  > 2012-08-08  Roland Schwingel  <roland.schwingel@onevision.com>
>  >
>  >       * generic/gdbtk-cmds.c (gdb_load_info): Replace call to
>  >       make_cleanup_bfd_close with make_cleanup_bfd_unref due
>  >       to changes in gdb.
>  >       (gdb_loc): Replace call to decode_line_spec with call to
>  >       decode_line_with_current_source due to changes in gdb.
>  >       * generic/gdbtk-wrapper.c: Comment unused functions
>  >       GDB_parse_exp_1 and wrap_parse_exp_1 as parse_exp_1 has
>  >       changed its interface and the code appears to be unused
>  >       anyway.
>  >       * generic/gdbtk-wrapper.h: ditto
>  >

Those changes look ok.

> parse_exp_1() in gdb has changed parameter count. As I wanted to adjust
> this in insight I found this code to be unused. To get insight compiling
> again I commented the affected functions. If no one objects I will
> remove this code (most of the wrapper code seems to be unused) when
> back from my vacations which start in 10 minutes.... ;-)

I can look into that. Now that I've been prodded, I'll kick off a build 
and see what happens.

Keith


      reply	other threads:[~2012-08-08 14:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-08 13:54 Roland Schwingel
2012-08-08 14:18 ` Keith Seitz [this message]

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=5022750D.4050207@redhat.com \
    --to=keiths@redhat.com \
    --cc=insight@sourceware.org \
    --cc=roland@onevision.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).