From: Tom Tromey <tromey@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/6] gdbserver: remove function abbrevs from debugging text
Date: Wed, 18 Dec 2013 15:13:00 -0000 [thread overview]
Message-ID: <87ob4embtf.fsf@fleche.redhat.com> (raw)
In-Reply-To: <52B0EF1E.7080302@codesourcery.com> (Yao Qi's message of "Wed, 18 Dec 2013 08:41:02 +0800")
>>>>> "Yao" == Yao Qi <yao@codesourcery.com> writes:
Yao> The function names in debugging output will be out of sync as function
Yao> names are changed, unless macro __func__ is used. However, __func__
Yao> is defined in C99 and we are using C90 (?) in GDB.
FWIW we found out a while back that gdbserver actually relies on GNU C
-- see the ax_debug and ax_debug_1 defines in ax.c. And, BFD
unconditionally uses "long long" in spots. So while the rule is
officially that gdb is C89, in practice that isn't actually true.
Tom
prev parent reply other threads:[~2013-12-18 15:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 21:43 Doug Evans
2013-12-18 0:42 ` Yao Qi
2013-12-18 1:20 ` Doug Evans
2013-12-18 1:57 ` Yao Qi
2013-12-18 11:16 ` Pedro Alves
2013-12-18 15:13 ` Tom Tromey [this message]
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=87ob4embtf.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=yao@codesourcery.com \
/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