From: Chris Nicol <nicolc@uleth.ca>
To: Martin Simmons <"martin@qqxnjvamvxwx"@dyxyl.com>
Cc: qqxnjvamvxwx@dyxyl.com, simark@simark.ca, gdb@sourceware.org
Subject: Re: gdb 8.3: "handler for the OSI ABI "FreeBSD" is not built into this configuration"
Date: Thu, 28 May 2020 11:37:59 -0600 [thread overview]
Message-ID: <99b17222-5d77-9e0e-0229-3cc24fc263c5@uleth.ca> (raw)
In-Reply-To: <jeeer4otkp.fsf@dyxyl.com>
Martin,
OK, great. So I now have an up-to-date gdb, at version 9.1. I will spend
some time figuring out how to use it. I am new to this, as you can
probably tell... I appreciate all of your assistance. I will take a
closer look at some of the llvm-tblgen code.
Chris.
On 5/28/2020 11:30 AM, Martin Simmons wrote:
>
> OK, that shows a reasonable set of registers and a reasonable backtrace.
> It shows that llvm-tblgen jumped to address 0 from inside __once_proxy
> for some reason.
>
> Gdb seems to be working, at least for this core file, so you can safely
> ignore the OS ABI warning.
>
> __Martin
>
next prev parent reply other threads:[~2020-05-28 17:38 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:24 gdb-9.1 Fails to build: "invalid cast to abstract class type" Chris Nicol
2020-05-21 14:12 ` Simon Marchi
2020-05-22 3:55 ` Chris Nicol
2020-05-22 5:56 ` gdb 8.3: "handler for the OSI ABI "FreeBSD" is not built into this configuration" Chris Nicol
2020-05-22 17:36 ` Simon Marchi
2020-05-22 18:22 ` Chris Nicol
2020-05-22 18:51 ` Simon Marchi
2020-05-22 19:35 ` Chris Nicol
2020-05-23 17:40 ` Martin Simmons
2020-05-23 18:29 ` Chris Nicol
2020-05-23 22:17 ` Martin Simmons
2020-05-24 1:55 ` Chris Nicol
2020-05-24 14:05 ` Simon Marchi
2020-05-27 21:31 ` Martin Simmons
[not found] ` <46566349-c023-6a75-7006-268aad4913c6@uleth.ca>
2020-05-28 10:57 ` Martin Simmons
2020-05-28 14:40 ` Chris Nicol
2020-05-28 17:30 ` Martin Simmons
2020-05-28 17:37 ` Chris Nicol [this message]
2020-05-23 16:29 ` gdb-9.1 Fails to build: "invalid cast to abstract class type" Joel Brobecker
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=99b17222-5d77-9e0e-0229-3cc24fc263c5@uleth.ca \
--to=nicolc@uleth.ca \
--cc="martin@qqxnjvamvxwx"@dyxyl.com \
--cc=gdb@sourceware.org \
--cc=qqxnjvamvxwx@dyxyl.com \
--cc=simark@simark.ca \
/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).