public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: "Insight (Эл. почта)" <insight@sourceware.cygnus.com>
Subject: RE: [bug] Synchonization of registers window in h8300 Insight
Date: Wed, 10 Oct 2001 10:57:00 -0000	[thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D56FF5F@clue.transas.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]

Hi Keith,

Sorry for previous bad reply.

> > GNU gdb 5.1
> > Copyright 2001 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public 
> License, and you are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show 
> warranty" for details.
> > This GDB was configured as "--host=i686-pc-cygwin 
> --target=h8300-hms".
> 
> Can you send me two very simple executables to demonstrate 
> the problem?
> (This prevents me from having to build compiler(s) and 
> figuring out how to
> build them.)
> 
> Please tell me the exact procedure you used to do this. Although I
> think I can guess, it never hurts to be sure. During this, please be
> explicit about what registers should appear when.
> 
> For example,
> 
> . load ex1.elf
> . break in main
> . run on simulator
> . open register window
> . notice registers foo, bar, baz
> (and so on)

I attach bzipped hello.out and hello.c (COFF with full gdb debug info).

Now, whats I do:

$h8300-hms-gdb
<Ctrl-R> (show regs. window)
Ok, Insight show me regs for h8300 (16 bits regs: r0...r6, sp, ccr ...)

Here started snapshot from console window ->
------------------------------------------------------
(gdb) show architecture 
The target architecture is set automatically (currently unknown)

(gdb) file hello.out
(gdb) ta si
Connected to the simulator.

(gdb) lo
Loading section .text, size 0xfc vma 0x100
Loading section .data, size 0x298 vma 0x1fc
Loading section .stack, size 0x4 vma 0x3fffc
Start address 0x102
Transfer rate: 7360 bits in <1 sec.

(gdb) show architecture 
The target architecture is set automatically (currently h8300s)

(gdb) set architecture h8300s
The target architecture is assumed to be h8300s

(gdb) show architecture 
The target architecture is assumed to be h8300s

(gdb) 
------------------------------------------------------

But Registers widow still show h8300 registers :((,
but must show: er0...er6, sp, ccr ...

> 
> BTW, I think a workaround for your problem is to simply close 
> the register
> window and re-open it, no?
> 
> Keith

It's not so good idea, because h8300 and h8300s have different number 
of hardware regs (it not implemented in current, but may will implement 
in future ver. of gdb), and if I forget close Regs. windows before 
changing architecture (through load or somehow else), then Insight 
(not gdb) will die when I will try close this window :(.

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.

Andrey


[-- Attachment #2: hello.tar.bz --]
[-- Type: application/octet-stream, Size: 1698 bytes --]

WARNING: multiple messages have this Message-ID
From: Andrew Volkov <Andrew.Volkov@transas.com>
To: Keith Seitz <keiths@cygnus.com>
Cc: "Insight (Эл. почта)" <insight@sourceware.cygnus.com>
Subject: RE: [bug] Synchonization of registers window in h8300 Insight
Date: Fri, 07 Dec 2001 11:07:00 -0000	[thread overview]
Message-ID: <2E74F312D6980D459F3A05492BA40F8D56FF5F@clue.transas.com> (raw)
Message-ID: <20011207110700.RZ9BEeJ3KxKDTIO5dUfyJG46AUTd3c3gOJ4QYWKJr28@z> (raw)

[-- Attachment #1: Type: text/plain, Size: 2733 bytes --]

Hi Keith,

Sorry for previous bad reply.

> > GNU gdb 5.1
> > Copyright 2001 Free Software Foundation, Inc.
> > GDB is free software, covered by the GNU General Public 
> License, and you are
> > welcome to change it and/or distribute copies of it under certain
> > conditions.
> > Type "show copying" to see the conditions.
> > There is absolutely no warranty for GDB.  Type "show 
> warranty" for details.
> > This GDB was configured as "--host=i686-pc-cygwin 
> --target=h8300-hms".
> 
> Can you send me two very simple executables to demonstrate 
> the problem?
> (This prevents me from having to build compiler(s) and 
> figuring out how to
> build them.)
> 
> Please tell me the exact procedure you used to do this. Although I
> think I can guess, it never hurts to be sure. During this, please be
> explicit about what registers should appear when.
> 
> For example,
> 
> . load ex1.elf
> . break in main
> . run on simulator
> . open register window
> . notice registers foo, bar, baz
> (and so on)

I attach bzipped hello.out and hello.c (COFF with full gdb debug info).

Now, whats I do:

$h8300-hms-gdb
<Ctrl-R> (show regs. window)
Ok, Insight show me regs for h8300 (16 bits regs: r0...r6, sp, ccr ...)

Here started snapshot from console window ->
------------------------------------------------------
(gdb) show architecture 
The target architecture is set automatically (currently unknown)

(gdb) file hello.out
(gdb) ta si
Connected to the simulator.

(gdb) lo
Loading section .text, size 0xfc vma 0x100
Loading section .data, size 0x298 vma 0x1fc
Loading section .stack, size 0x4 vma 0x3fffc
Start address 0x102
Transfer rate: 7360 bits in <1 sec.

(gdb) show architecture 
The target architecture is set automatically (currently h8300s)

(gdb) set architecture h8300s
The target architecture is assumed to be h8300s

(gdb) show architecture 
The target architecture is assumed to be h8300s

(gdb) 
------------------------------------------------------

But Registers widow still show h8300 registers :((,
but must show: er0...er6, sp, ccr ...

> 
> BTW, I think a workaround for your problem is to simply close 
> the register
> window and re-open it, no?
> 
> Keith

It's not so good idea, because h8300 and h8300s have different number 
of hardware regs (it not implemented in current, but may will implement 
in future ver. of gdb), and if I forget close Regs. windows before 
changing architecture (through load or somehow else), then Insight 
(not gdb) will die when I will try close this window :(.

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.

Andrey


[-- Attachment #2: hello.tar.bz --]
[-- Type: application/x-bzip2, Size: 1698 bytes --]

             reply	other threads:[~2001-12-07 19:07 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-10 10:57 Andrew Volkov [this message]
2001-10-11  7:53 ` Andrew Cagney
2001-12-07 13:30   ` Andrew Cagney
2001-12-07 11:07 ` Andrew Volkov
  -- strict thread matches above, loose matches on Subject: below --
2001-10-11  9:38 Andrew Volkov
2001-12-08  6:57 ` Andrew Volkov
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
     [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=2E74F312D6980D459F3A05492BA40F8D56FF5F@clue.transas.com \
    --to=andrew.volkov@transas.com \
    --cc=insight@sourceware.cygnus.com \
    --cc=keiths@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).