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 tdep/12797] New: GDB is unable to do inf-call of return type _Complex on armv7l-unknown-linux-gnueabi
Date: Mon, 23 May 2011 14:30:00 -0000	[thread overview]
Message-ID: <bug-12797-4717@http.sourceware.org/bugzilla/> (raw)

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

           Summary: GDB is unable to do inf-call of return type _Complex
                    on armv7l-unknown-linux-gnueabi
           Product: gdb
           Version: HEAD
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tdep
        AssignedTo: unassigned@sourceware.org
        ReportedBy: qiyao@gcc.gnu.org
              Host: armv7l-unknown-linux-gnueabi
            Target: armv7l-unknown-linux-gnueabi
             Build: armv7l-unknown-linux-gnueabi


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

inferior gets SEGV when gdb does inf-call of returning _Complex
{float|double|long double}.

$ gcc -marm -g ~/complex-ret.c -o complex-ret
$ ./gdb ./complex-ret
(gdb) b main
Breakpoint 1 at 0x8368: file /home/yao/complex-ret.c, line 9.
(gdb) run
Starting program: /home/yao/gdb/gdb-fsf-git/build/gdb/complex-ret

Breakpoint 1, main () at /home/yao/complex-ret.c:9
9         return 0;
(gdb) p return_double_complex (dc)
During symbol reading, incomplete CFI data; unspecified registers (e.g., r0) at
0x8368.

Program received signal SIGSEGV, Segmentation fault.
0x000083d0 in return_double_complex (dc=4 + 1.146232298351692e-321 * I) at
/home/yao/complex-ret.c:21
21        return dc;
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
(return_double_complex) will be abandoned.
When the function is done executing, GDB will silently stop.

(gdb) p return_float_complex (fc)

Program received signal SIGSEGV, Segmentation fault.
0x00008398 in return_float_complex (fc=2 + 0 * I) at /home/yao/complex-ret.c:15
15        return fc;
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
(return_float_complex) will be abandoned.
When the function is done executing, GDB will silently stop.

(gdb) p return_long_double_complex (ldc)

Program received signal SIGSEGV, Segmentation fault.
0x0000840c in return_long_double_complex (ldc=6 + 4.2991634724961358e-311 * I)
at /home/yao/complex-ret.c:27
27        return ldc;
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
(return_long_double_complex) will be abandoned.
When the function is done executing, GDB will silently stop.

-- 
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-23 14:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-23 14:30 qiyao at gcc dot gnu.org [this message]
2011-12-21 21:13 ` [Bug tdep/12797] " cvs-commit at gcc dot gnu.org
2011-12-21 21:17 ` cvs-commit at gcc dot gnu.org
2011-12-21 21:30 ` uweigand at gcc dot gnu.org
2011-12-21 21:31 ` uweigand at gcc dot gnu.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-12797-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).