public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Paul Schlie <schlie@comcast.net>
To: Keith Seitz <keiths@redhat.com>
Cc: "insight@sources.redhat.com" <insight@sources.redhat.com>
Subject: Re: [patch] updates gdbtk to use lbasename() do to shared lib header tweaks.
Date: Fri, 27 May 2005 04:48:00 -0000	[thread overview]
Message-ID: <BEBC1EB3.A4A8%schlie@comcast.net> (raw)
In-Reply-To: <1117157462.4456.117.camel@lindt.uglyboxes.com>

> From: Keith Seitz <keiths@redhat.com>
>> On Thu, 2005-05-26 at 19:09 -0400, Paul Schlie wrote:
>> (patch enclosed as an attachment, so don't know if it's visible on boards)
> 
> Hmm. For some reason, I could not apply your patch. Goofy. Fortunately,
> it was simple enough.
> 
> I have also take the opportunity to remove a few other compiler warnings
> stemming from some gdb "API" changes from char* to gdb_byte*.
> 
> I tried to run this through the testsuite, but I see that varobj.c is
> throwing an internal error trying to run c_variable.exp. :-(

Thank you. With respect to the test-suite failure, I'm embarrassed to admit
that I've never actually run it, as for some reason which I haven't looked
close enough to know why, it's not being built by default when I configure
and build the entire source tree (so correspondingly have never run it),
but things seem to be ok (but haven't applied your latest tweaks yet
which should only help), but suspect its possible something subtle is
wrong that the test-suite is catching that I haven't seen or noticed?


  reply	other threads:[~2005-05-27  4:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-26 23:09 Paul Schlie
2005-05-27  1:31 ` Keith Seitz
2005-05-27  4:48   ` Paul Schlie [this message]
2005-05-27  6:07     ` Keith Seitz

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=BEBC1EB3.A4A8%schlie@comcast.net \
    --to=schlie@comcast.net \
    --cc=insight@sources.redhat.com \
    --cc=keiths@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).