public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: debug/1621: Debugging with complex numbers Date: Sat, 07 Dec 2002 17:26:00 -0000 [thread overview] Message-ID: <20021208012601.10009.qmail@sources.redhat.com> (raw) The following reply was made to PR debug/1621; it has been noted by GNATS. From: Daniel Jacobowitz <drow@mvista.com> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: "Joseph S. Myers" <jsm28@cam.ac.uk>, bangerth@dealii.org, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: debug/1621: Debugging with complex numbers Date: Sat, 7 Dec 2002 20:21:24 -0500 On Thu, Dec 05, 2002 at 06:09:46PM -0600, Wolfgang Bangerth wrote: > > > > > Joseph, this report is now almost 2 years old, and versions > > > 3.0 and 3.1/2 have happened in between. Unfortunately, there > > > are no testcases in the report, so I can't check the claims > > > myself, but do you know whether the situation has or has > > > not improved in the meantime? > > > > The testcase is at the URL given in the report > > <http://gcc.gnu.org/ml/gcc/2000-12/msg00536.html>: > > Oh, sorry, I seem to have overlooked this. > > > > static __complex__ double x = 2.0 + 3.0i; > > int main(void) > > { > > return 0; > > } > > > > (gdb) p x > > $1 = Invalid C/C++ type code 20 in symbol table. > > (gdb) p x$real > > No symbol "x$real" in current context. > > (gdb) p x$imag > > No symbol "x$imag" in current context. > > This is also the behavior I get, using 3.3CVS and gdb5.1.1. For some > reason, I cannot get gdb CVS compiled, so can't check whether it works > now. The gdb error message indicates that gcc is doing something but gdb > isn't understanding it. > > Daniel, I'm CC:ing you since you wrote the latest mail I could find on the > gdb mailing lists that is about complex value support > http://sources.redhat.com/ml/gdb/2002-01/msg00359.html > > In this you state that you had been fixing some problems. Do you know > anything about gdb's present support for complex values? GDB is fine; GCC is broken. You'll find that in recent GCC and GDB DWARF-2 will work fine. Stabs will fail; the debugging output from GCC is inconsistent. Someone should probably fix it to use the Sun notation for such variables (i.e. "R" instead of "r", IIRC). -- Daniel Jacobowitz MontaVista Software Debian GNU/Linux Developer
next reply other threads:[~2002-12-08 1:26 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2002-12-07 17:26 Daniel Jacobowitz [this message] -- strict thread matches above, loose matches on Subject: below -- 2002-12-28 10:59 jsm28 2002-12-13 11:26 Joseph S. Myers 2002-12-13 9:32 wilson 2002-12-12 14:16 Jim Wilson 2002-12-12 13:36 Jim Wilson 2002-12-12 11:56 Daniel Jacobowitz 2002-12-12 7:56 Jim Wilson 2002-12-11 17:26 Daniel Jacobowitz 2002-12-11 16:16 Jim Wilson 2002-12-09 12:24 bangerth 2002-12-05 16:16 Wolfgang Bangerth 2002-12-05 15:26 Joseph S. Myers 2002-12-05 12:09 bangerth 2001-04-01 0:00 Joseph Myers
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=20021208012601.10009.qmail@sources.redhat.com \ --to=drow@mvista.com \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@gcc.gnu.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: linkBe 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).