This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tdep/12798] New: Failed to pass _Complex args in value


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

           Summary: Failed to pass _Complex args in value
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
        AssignedTo: unassigned@sourceware.org
        ReportedBy: qiyao@gcc.gnu.org
              Host: x86_64-linux
            Target: x86_64-linux
             Build: x86_64-linux


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

GDB doesn't pass _Complex args in value in a correct way.

Here are the steps to reproduce it,

$ gcc -g complex-value.c -o complex-value
$ ./gdb ./complex-value
(gdb) b main
Breakpoint 1 at 0x4008b5: file /scratch/yao/complex-value.c, line 58.
(gdb) run
Starting program: /scratch/yao/gdb_cvs/build-x86_64/gdb/compllex-value

Breakpoint 1, main () at /scratch/yao/complex-value.c:58
58        return 0;
(gdb) p t_float_complex_values(fc1, fc2)
During symbol reading, incomplete CFI data; unspecified registers (e.g., rax)
at 0x4008b5.
$1 = 0  // <-- wrong.  1 is expected here.
(gdb) p t_double_complex_values(dc1, dc2)
$2 = 0  // <-- wrong.  1 is expected here.
(gdb) p t_long_double_complex_values(ldc1, ldc2)
$3 = 1  // <-- correct.

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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]