public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug tdep/13766] New: [7.3/7.4 Regression] "info vec" and info "float" don't work with AVX
Date: Mon, 27 Feb 2012 17:06:00 -0000	[thread overview]
Message-ID: <bug-13766-4717@http.sourceware.org/bugzilla/> (raw)

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

             Bug #: 13766
           Summary: [7.3/7.4 Regression] "info vec" and info "float" don't
                    work with AVX
           Product: gdb
           Version: 7.4
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
        AssignedTo: unassigned@sourceware.org
        ReportedBy: hjl.tools@gmail.com
    Classification: Unclassified


On Fedora 15/x86-64 with AVX support, gdb 7.3/7.4 give

GNU gdb (GDB) Fedora (7.3.1-47.fc15)
Copyright (C) 2011 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /export/home/hjl/bugs/gdb/vdso/64...done.
Setting up the environment for debugging gdb.
Function "internal_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) [answered N;
input not from terminal]
Function "info_command" not defined.
Make breakpoint pending on future shared library load? (y or [n]) [answered N;
input not from terminal]
.gdbinit:8: Error in sourced command file:
Argument required (one or more breakpoint numbers).
(gdb) b main
Breakpoint 1 at 0x4005a7: file sleepalot.c, line 12.
(gdb) r
Starting program: /export/home/hjl/bugs/gdb/vdso/64 

Breakpoint 1, main (argc=1, argv=0x7fffffffe3d8) at sleepalot.c:12
12       printf("I'm process %d\n", getpid());
Missing separate debuginfos, use: debuginfo-install glibc-2.14.1-6.1.x86_64
(gdb) info float
  R7: Empty   Register 31 is not available
(gdb) info vec
mxcsr          0x1f80    [ IM DM ZM OM UM PM ]
ymm0           *value not available*
ymm1           *value not available*
ymm2           *value not available*
ymm3           *value not available*
ymm4           *value not available*
ymm5           *value not available*
ymm6           *value not available*
ymm7           *value not available*
ymm8           *value not available*
ymm9           *value not available*
ymm10          *value not available*
ymm11          *value not available*
ymm12          *value not available*
ymm13          *value not available*
ymm14          *value not available*
ymm15          *value not available*
(gdb)

-- 
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:[~2012-02-27 17:06 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 17:06 hjl.tools at gmail dot com [this message]
2012-02-27 17:31 ` [Bug tdep/13766] " palves at redhat dot com
2012-02-27 17:49 ` palves at redhat dot com
2012-02-27 18:06 ` hjl.tools at gmail dot com
2012-03-05 14:25 ` cvs-commit at gcc dot gnu.org
2012-03-05 14:34 ` palves at redhat dot com
2012-03-05 17:19 ` hjl.tools at gmail dot com
2012-03-05 17:24 ` palves at redhat dot com
2012-03-06 13:17 ` cvs-commit at gcc dot gnu.org
2012-03-06 13:20 ` cvs-commit at gcc dot gnu.org
2012-03-06 13:21 ` palves at redhat dot com

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-13766-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).