From: Chris Nicol <nicolc@uleth.ca>
To: gdb@sourceware.org
Subject: Re: gdb-9.1 Fails to build: "invalid cast to abstract class type"
Date: Thu, 21 May 2020 21:55:55 -0600 [thread overview]
Message-ID: <198ff4bc-8195-750e-84f5-e3d76974a223@uleth.ca> (raw)
In-Reply-To: <1b20f6d8-9736-02d8-73dc-bc4843e36ed3@simark.ca>
Dear Simon,
Thanks for your helpful advice. Before receiving it, I retrieved version
8.3 looking for a different result, and your advice arrived just as that
version crashed for the same reason. So, I did the edit on the relevant
code, and this version failed at the very end when doing all the
linking. I was able to find the fix for that fail from git, and built
the 8.3 successfully. I am now in the process of building 9.1 with the
fix you have noted. The SunBlade 100 is old, so this will take some
time, but I am pretty sure it will work now. Thanks for the offer of the
9.2. I will just wait until that is formally released. I have been
pulling these src files from ftp.gnu.org, but it might be a better idea
to go get the code from git, as it would incorporate any intermediate
bug fixes?
The reason I wanted the new version of debugger was because the older
one I had (a stock 6.1.1, which came with the FreeBSD 12.1 I am running)
would not run against some core dumps I had from llvm-tblgen in the
build of llvm90. This was being built with gcc9, a gcc9 which I built
and installed on the SunBlade 100 from the /usr/ports tree. When I run
the gdb-8.3 against that llvn-tblgen.core, I get an initial message "A
handler for the OSI ABI "FreeBSD" is not built into this configuration
of GDB. Attempting to continue with the default sparc settings". The
debugger does not then provide any useful results, simply indicating
that a seg fault happened at:
#0 0000000000000000 in ?? ()
I think this is because the gdb can't figure out the arch of my
SunBlade? I read some other posts of a similar nature that generated
this message, which I think is built into the test code to identify
architecture. I believe there is a simple workaround for this, but it is
beyond my ken as a mere economist dabbling in things I should leave alone ;)
Can anyone of the list provide any advice on this, please? Thank you.
Sincerely,
Chris.
> On 5/21/2020 8:12 AM, Simon Marchi wrote:
>>
>> This has been fixed by this commit:
>>
>>
>> https://sourceware.org/git/?p=binutils-gdb.git;a=commit;h=c6a42d11acf2d485bf70d76eda76fd005fcd6825
>>
>>
>> So if you use the master branch, you shouldn't see this error.
>>
>> GDB 9.2 (the bugfix release of 9.1) will be out soon, we could probably
>> cherry-pick that commit in that branch if that helps you.
>>
>> Simon
>>
>
>
>
next prev parent reply other threads:[~2020-05-22 3:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-20 18:24 Chris Nicol
2020-05-21 14:12 ` Simon Marchi
2020-05-22 3:55 ` Chris Nicol [this message]
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
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=198ff4bc-8195-750e-84f5-e3d76974a223@uleth.ca \
--to=nicolc@uleth.ca \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).