From: Pedro Alves <palves@redhat.com>
To: John Baldwin <jhb@freebsd.org>, Chris Johns <chrisj@rtems.org>
Cc: gdb@sourceware.org
Subject: Re: gdb-7.12 powerpc-rtems4.12-gdb does not build on FreeBSD.
Date: Thu, 24 Nov 2016 14:02:00 -0000 [thread overview]
Message-ID: <2c9c6609-437d-a4a1-23d5-432aa0414eb7@redhat.com> (raw)
In-Reply-To: <83274785-223a-952d-f881-eda75b94599d@redhat.com>
On 11/24/2016 12:33 PM, Pedro Alves wrote:
> On 11/24/2016 12:12 PM, Pedro Alves wrote:
>
>> The PPC sim shouldn't be calling GDB's "error" directly. If it does,
>> then that's should be fixed. There's an "error" method in the
>> host_callback structure (filled in by GDB) that should be used instead.
>
> I tried reproducing on GNU/Linux here, but it doesn't. Looks like
> "error" ends up resolved to something, most probably glibc's own
> "error" function (a GNU extension):
>
> https://linux.die.net/man/3/error
>
> So on GNU/Linux those sim "error" calls probably crash at run time.
I've started writing a patch, and there are sooo many "error" calls
all over this sim... It'll be a larger patch than I thought.
For 7.12.1, the simplest would probably be to give GDB's "error"
function extern "C" linkage.
Meanwhile, if you're not interested in the sim,
you should be able to workaround this by configuring
with --disable-sim.
Chris, could you open a bug report in bugzilla?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2016-11-24 14:02 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-22 23:38 Chris Johns
2016-11-23 23:16 ` Chris Johns
2016-11-24 0:16 ` John Baldwin
2016-11-24 0:30 ` Chris Johns
2016-11-24 2:48 ` John Baldwin
2016-11-24 12:12 ` Pedro Alves
2016-11-24 12:33 ` Pedro Alves
2016-11-24 14:02 ` Pedro Alves [this message]
2016-11-25 0:21 ` Chris Johns
2016-11-25 1:21 ` Pedro Alves
2016-11-25 4:06 ` Chris Johns
2016-11-24 14:19 ` John Baldwin
2016-11-24 14:59 ` Pedro Alves
2016-11-24 17:47 ` John Baldwin
2016-11-24 18:52 ` Pedro Alves
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=2c9c6609-437d-a4a1-23d5-432aa0414eb7@redhat.com \
--to=palves@redhat.com \
--cc=chrisj@rtems.org \
--cc=gdb@sourceware.org \
--cc=jhb@freebsd.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