public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: Bernhard Walle <Bernhard.Walle@gmx.de>
To: kseitz@sources.redhat.com
Cc: insight-prs@sources.redhat.com,
Subject: Re: insight/259: View/Registers leads to internal error
Date: Tue, 27 Jul 2004 18:43:00 -0000	[thread overview]
Message-ID: <20040727184301.4600.qmail@sourceware.org> (raw)

The following reply was made to PR insight/259; it has been noted by GNATS.

From: Bernhard Walle <Bernhard.Walle@gmx.de>
To: insight-gnats@sources.redhat.com
Cc:  
Subject: Re: insight/259: View/Registers leads to internal error
Date: Tue, 27 Jul 2004 20:40:40 +0200

 I had the same problem with a own target (MVME-162 `68k-bug' for m68k
 CPU), very similar to cpu32bug. Your described solution solved the
 problem.
 
 


             reply	other threads:[~2004-07-27 18:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-27 18:43 Bernhard Walle [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-26 22:53 E. Weddington
2005-01-25 19:23 E. Weddington
2004-07-07 15:21 kseitz
2004-07-07  8:03 lars.friedrich

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=20040727184301.4600.qmail@sourceware.org \
    --to=bernhard.walle@gmx.de \
    --cc=insight-prs@sources.redhat.com \
    --cc=kseitz@sources.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).