From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: RE: [bug] Synchonization of registers window in h8300 Insight
Date: Thu, 11 Oct 2001 09:38:00 -0000 [thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D56FF82@clue.transas.com> (raw)
Ok, I'm ready to start converting h8300 part of GDB to multi-arch.
Andrey
> -----Original Message-----
> From: Andrew Cagney [mailto:ac131313@cygnus.com]
> Sent: Saturday, December 08, 2001 12:31 AM
> To: Andrew Volkov
> Cc: Keith Seitz; Insight
> Subject: Re: [bug] Synchonization of registers window in h8300 Insight
>
>
> > Another warkaround, NETHER run gdb without args (ex. $h8300-hms-gdb
> > hello.out).
> >
> > But, I think better way remain registers window blank (if
> it possible), or
> > invisible while architecture is unknown.
>
> Unfortunatly the architecture is known. GDB makes use of
> that default
> architecture when talking to some targets.
>
> The best way to fix this really is multi-arch - all sorts of problems
> just mysteriously disappear! Would you (FSF assignment
> permitting) be
> interested in helping with converting the h8300 to multi-arch?
>
> Andrew
WARNING: multiple messages have this Message-ID
From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Andrew Cagney <ac131313@cygnus.com>
Cc: insight@sourceware.cygnus.com
Subject: RE: [bug] Synchonization of registers window in h8300 Insight
Date: Sat, 08 Dec 2001 06:57:00 -0000 [thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D56FF82@clue.transas.com> (raw)
Message-ID: <20011208065700.IX0tMHBzw7kWlONXHmQtFtcUhXCpDAFpRvIu3mMkZzU@z> (raw)
Ok, I'm ready to start converting h8300 part of GDB to multi-arch.
Andrey
> -----Original Message-----
> From: Andrew Cagney [ mailto:ac131313@cygnus.com ]
> Sent: Saturday, December 08, 2001 12:31 AM
> To: Andrew Volkov
> Cc: Keith Seitz; Insight
> Subject: Re: [bug] Synchonization of registers window in h8300 Insight
>
>
> > Another warkaround, NETHER run gdb without args (ex. $h8300-hms-gdb
> > hello.out).
> >
> > But, I think better way remain registers window blank (if
> it possible), or
> > invisible while architecture is unknown.
>
> Unfortunatly the architecture is known. GDB makes use of
> that default
> architecture when talking to some targets.
>
> The best way to fix this really is multi-arch - all sorts of problems
> just mysteriously disappear! Would you (FSF assignment
> permitting) be
> interested in helping with converting the h8300 to multi-arch?
>
> Andrew
next reply other threads:[~2001-12-08 14:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-11 9:38 Andrew Volkov [this message]
2001-12-08 6:57 ` Andrew Volkov
-- strict thread matches above, loose matches on Subject: below --
2001-10-10 19:42 Andrew Volkov
2001-10-10 21:31 ` Elena Zannoni
2001-12-07 11:50 ` Elena Zannoni
2001-12-07 11:42 ` Andrew Volkov
2001-10-10 10:57 Andrew Volkov
2001-10-11 7:53 ` Andrew Cagney
2001-12-07 13:30 ` Andrew Cagney
2001-12-07 11:07 ` Andrew Volkov
[not found] <2E74F312D6980D459F3A05492BA40F8D56FF5A@clue.transas.com>
2001-10-10 10:15 ` Keith Seitz
2001-12-07 10:06 ` Keith Seitz
2001-10-10 9:42 Andrew Volkov
2001-10-10 9:54 ` Keith Seitz
2001-10-10 18:06 ` Andrew Cagney
2001-12-07 11:08 ` Andrew Cagney
2001-12-07 9:58 ` Keith Seitz
2001-12-07 9:49 ` Andrew Volkov
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=2E74F312D6980D459F3A05492BA40F8D56FF82@clue.transas.com \
--to=andrew.volkov@transas.com \
--cc=ac131313@cygnus.com \
--cc=insight@sourceware.cygnus.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).