From: Joel Sherrill <joel.sherrill@oarcorp.com>
To: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Multiple Target Failures for Multiple Definition of debug_printf
Date: Thu, 21 Aug 2014 14:59:00 -0000 [thread overview]
Message-ID: <53F60937.2030404@oarcorp.com> (raw)
Hi
I reported this earlier but wanted to provide some more details.
Multiple architectures fail when linking gdb due to debug_printf()
being multiply defined.
The architectures are: bfin, h8300, lm32, mips, moxie, and v850.
The debug_printf() in gdb/common/common-debug.c is very
simple. But the one in sim/common/sim-trace.c is more
complicated and has awareness of the simulator state.
Thus they can't be folded into one method.
There are 7 calls to debug_printf() in the sim/ tree but 203
in the gdb/ tree.
This all leads me to believe that the solution is to change
the name of the debug_printf() in sim/ to something like
sim_debug_printf().
Thoughts?
--
Joel Sherrill, Ph.D. Director of Research & Development
joel.sherrill@OARcorp.com On-Line Applications Research
Ask me about RTEMS: a free RTOS Huntsville AL 35805
Support Available (256) 722-9985
next reply other threads:[~2014-08-21 14:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-21 14:59 Joel Sherrill [this message]
2014-08-21 15:49 ` Joel Sherrill
2014-08-27 8:48 ` Gary Benson
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=53F60937.2030404@oarcorp.com \
--to=joel.sherrill@oarcorp.com \
--cc=gdb@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