public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "wmealing at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tui/13073] New: TUI doesn't display registers in layout reg
Date: Wed, 10 Aug 2011 15:44:00 -0000	[thread overview]
Message-ID: <bug-13073-4717@http.sourceware.org/bugzilla/> (raw)

http://sourceware.org/bugzilla/show_bug.cgi?id=13073

             Bug #: 13073
           Summary: TUI doesn't display registers in layout reg
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
        AssignedTo: unassigned@sourceware.org
        ReportedBy: wmealing@gmail.com
    Classification: Unclassified


Created attachment 5891
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5891
Rubbish code i was messing with.

As the subject says, it doesn't look like the registers are showing on this
system.

Dual core system:

cpu family      : 6
model           : 15
model name      : Intel(R) Core(TM)2 Duo CPU     T7500  @ 2.20GHz
stepping        : 11

Compiled with:

# gcc -O0 -S -g -m32 -nostdlib binsearch.s -o binsearch

# gdb binsearch
GNU gdb (GDB) Fedora (7.3-41.fc15)
<snip>

(gdb) layout regs
(gdb) break 1
Breakpoint 1 at    0x4000b0: file binsearch.s, line 1.
(gdb) run
Starting program: /home/wmealing/Documents/workspace/asm/binsearch 
Register 57 is not available
Register 57 is not available
(gdb) i r

rax               0x0    0
rbx               0x0    0
rcx               0x0    0
rdx               0x0    0
rsi               0x0    0
rdi               0x0    0
rbp               0x0    0x0
rsp               0x7fffffffe1a0    0x7fffffffe1a0
r8                0x0    0
r9                0x0    0
r10               0x0    0
r11               0x200    512
r12               0x0    0
r13               0x0    0

etc.. etc


Interestingly it also gives 

"Warning: the current language does not match this frame"

I expected registers to appear as i step through the assembly code.

gdb-7.3-41.fc15.x86_64
glibc-common-2.14-4.x86_64
glibc-2.14-4.i686
glibc-2.14-4.x86_64

I'm going to attach the simple , unfinished code that i was playing around in.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


             reply	other threads:[~2011-08-10 15:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-10 15:44 wmealing at gmail dot com [this message]
2011-08-10 16:29 ` [Bug tui/13073] " pedro at codesourcery dot com
2011-08-10 18:30 ` pedro at codesourcery dot com
2011-08-10 19:31 ` pedro at codesourcery dot com
2011-08-11 16:50 ` wmealing at gmail dot com
2011-08-12 17:06 ` cvs-commit at gcc dot gnu.org
2011-08-12 17:19 ` cvs-commit at gcc dot gnu.org
2011-08-12 17:41 ` pedro at codesourcery dot com
2011-08-13 16:47 ` pedro at codesourcery dot com
2011-10-26 20:22 ` tristanmoody at gmail dot com
2014-02-16 18:27 ` jackie.rosen at hushmail dot com
2014-05-28 19:45 ` schwab at sourceware dot org

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=bug-13073-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /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).