public inbox for insight-prs@sourceware.org
help / color / mirror / Atom feed
From: lars.friedrich@wago.com
To: insight-gnats@sources.redhat.com
Subject: insight/259: View/Registers leads to internal error
Date: Wed, 07 Jul 2004 08:03:00 -0000	[thread overview]
Message-ID: <20040707075908.3411.qmail@sourceware.org> (raw)


>Number:         259
>Category:       insight
>Synopsis:       View/Registers leads to internal error
>Confidential:   no
>Severity:       critical
>Priority:       high
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Wed Jul 07 08:03:00 UTC 2004
>Closed-Date:
>Last-Modified:
>Originator:     lars.friedrich@wago.com
>Release:        insight-6.1
>Organization:
>Environment:
gcc version 3.3 20030226 (prerelease) (SuSe Linux)
SuSe Linux 8.2
insight compiled with ./configure --host=i686-pc-linux-gnu --target=arm-elf
using target ARM Angel via Ethernet, but error happens with target Simulator, too
>Description:
Selecting View/Registers while debugging any target application will always pop-up an error window:
gdbarch.c: 3906: internal-error: gdbarch_deprecated_register_convertible: Assertion 'gdbarch->deprectated_ (the rest of line cut off)
A problem internal to GDB has been detected,
further debugging may prove unreliable.

This problem did not exist with insight-6.0 (or 5.3)
>How-To-Repeat:
Start (arm-elf-)insight
View-Registers
Run-Connect to Target: Target: Simulator OK

It's not necessary to actually load an application to trigger the bug.
Opening the registers window prior the attempt to connect will not trigger the bug but will the moment, the connection attempt is made.
>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2004-07-07  8:03 UTC|newest]

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

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=20040707075908.3411.qmail@sourceware.org \
    --to=lars.friedrich@wago.com \
    --cc=insight-gnats@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).