public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "qiyao at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/12790] New: GDB is unable to do inf-call of vararg of type _Complex on x86_64-linux
Date: Fri, 20 May 2011 14:04:00 -0000	[thread overview]
Message-ID: <bug-12790-4717@http.sourceware.org/bugzilla/> (raw)

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

           Summary: GDB is unable to do inf-call of vararg of type
                    _Complex on x86_64-linux
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: gdb
        AssignedTo: unassigned@sourceware.org
        ReportedBy: qiyao@gcc.gnu.org


Created attachment 5741
  --> http://sourceware.org/bugzilla/attachment.cgi?id=5741
test case

GDB on x86_64-linux is unable to handl inf-call of vararg function of parameter
type _Complex.  Here are the steps to reproduce.

$ gcc -g complex.c -o complex

$ ./gdb/gdb complex
...
(gdb) b main
(gdb) run
Starting program: /scratch/yao/gdb_cvs/build-x86_64/complex

Breakpoint 1, main () at ../../complex.c:25
25        return 0;
(gdb) print find_max_float_real(4, fc1, fc2, fc3, fc4)
During symbol reading, incomplete CFI data; unspecified registers (e.g., rax)
at 0x40044c.
$1 = 0 + 0 * I  <-- wrong result.
(gdb) print find_max_double_real(4, dc1, dc2, dc3, dc4)
$2 = 0 + 0 * I  <-- wrong result.

(gdb) print find_max_long_double_real(4, ldc1, ldc2, ldc3, ldc4)
../../src/gdb/amd64-tdep.c:622: internal-error: amd64_return_value: Assertion
`len <= 16' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n) n

../../src/gdb/amd64-tdep.c:622: internal-error: amd64_return_value: Assertion
`len <= 16' failed.
A problem internal to GDB has been detected,

-- 
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-05-20 14:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-20 14:04 qiyao at gcc dot gnu.org [this message]
2011-05-23 14:33 ` [Bug tdep/12790] " qiyao at gcc dot gnu.org
2012-10-24 13:35 ` jan.kratochvil at redhat dot com
2012-10-25  8:59 ` cvs-commit at gcc dot gnu.org
2012-10-25  9:00 ` kettenis at gnu 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-12790-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).