public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: kseitz@sources.redhat.com
To: insight-prs@sources.redhat.com, kseitz@sources.redhat.com,
	nobody@sources.redhat.com, ulf.samuelsson@atmel.com
Subject: Re: insight/353: Insight-6.9.1 Build failure on Ubuntu 10.04 LTS x86
Date: Wed, 10 Nov 2010 19:35:00 -0000	[thread overview]
Message-ID: <20101110193503.2748.qmail@sourceware.org> (raw)

Synopsis: Insight-6.9.1 Build failure on Ubuntu 10.04 LTS x86

Responsible-Changed-From-To: unassigned->kseitz
Responsible-Changed-By: kseitz
Responsible-Changed-When: Wed Nov 10 19:35:03 2010
Responsible-Changed-Why:
    mine
State-Changed-From-To: open->closed
State-Changed-By: kseitz
State-Changed-When: Wed Nov 10 19:35:03 2010
State-Changed-Why:
    Thank you for the bug report. Normally, this bug should have been filled against gdb, since the errors occur within files owned by the gdb group.
    
    However, since 6.8, gdb has changed considerably, and I believe that almost all of the problems you have reported (and graciously provided patches for) have been addressed. The only problems that might still exist is the new_tty problem, but that code has changed considerably.
    
    I would encourage you to double-check this all against a newer gdb (7.2 was recently released). I am behind on making an insight release, but I hope to do that in the next couple of weeks.
    
    Thank you again for your help!

http://sourceware.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=insight&pr=353


             reply	other threads:[~2010-11-10 19:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-10 19:35 kseitz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-07 21:23 ulf.samuelsson

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=20101110193503.2748.qmail@sourceware.org \
    --to=kseitz@sources.redhat.com \
    --cc=insight-gnats@sources.redhat.com \
    --cc=insight-prs@sources.redhat.com \
    --cc=nobody@sources.redhat.com \
    --cc=ulf.samuelsson@atmel.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).