[Bug gdb/12776] New: GDB is unable to do inf-call of vararg of type_Complex

["qiyao at gcc dot gnu.org" <sourceware-bugzilla at sourceware dot org>]

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

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


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

GDB can't do inf-all of vararg functions if parameters' type is double _Complex
and long double _Complex.

Here are the steps to reproduce this problem on x86-linux

$ gcc -g complex.c -o complex
$./gdb complex
...

Breakpoint 1, main () at complex.c:19
19      return 0;
(gdb) print find_max_double_real(4, dc1, dc2, dc3, dc4)
During symbol reading, incomplete CFI data; unspecified registers (e.g., eax)
at 0x80483b7.

Program received signal SIGSEGV, Segmentation fault.
0x08048423 in find_max_double_real (num_vals=0) at complex.c:37
37      return max;
The program being debugged was signaled while in a function called from GDB.
GDB remains in the frame where the signal was received.
To change this behavior use "set unwindonsignal on".
Evaluation of the expression containing the function
(find_max_double_real) will be abandoned.
When the function is done executing, GDB will silently stop.

We can get similar error if parameter's type is long double _Complex.  However,
gdb works well when parameter's type is float _Complex.

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