From: Chris Nicol <nicolc@uleth.ca>
To: Martin Simmons <qqxnjvamvxwx@dyxyl.com>
Cc: simark@simark.ca, gdb@sourceware.org
Subject: Re: gdb 8.3: "handler for the OSI ABI "FreeBSD" is not built into this configuration"
Date: Sat, 23 May 2020 19:55:05 -0600 [thread overview]
Message-ID: <fde90674-fb5e-14de-7ab1-03d51b7d99ad@uleth.ca> (raw)
In-Reply-To: <jeh7w6b8j2.fsf@dyxyl.com>
Thanks, Martin. Yes, when the gdb_6.1.1 did not work, I first had a look
to build the 9.1 in /usr/ports/devel/gdb, but the Makefile indicates
NOT_FOR_ARCHS= sparc64, and a comment above it "untested on sparc64,
might work". Not encouraged, I went on to build the 9.1 from the gnu
source. Maybe I will try the /usr/ports version if I comment out the
NOT_FOR_ARCHS, since there might be some tweaks in there that is
specific to FreeBSD.
I will also try what you are suggesting below. Hard to track down the
llvm-tblgen problem when I can't debug why it is seg. faulting... and
getting some help on the llvm list has been pretty fruitless.
Chris.
On 5/23/2020 4:17 PM, Martin Simmons wrote:
> Hi Chris,
>
> Yes, the architecture is detected from the binary if given, otherwise it
> defaults to the main architecture.
>
> BTW, have you tried building devel/gdb from the /usr/ports tree? That
> is the normal way to get any specific tweaks that the FreeBSD project
> already knows about.
>
> I can't give you comprehensive instructions on how to debug the nested
> gdb. I think you should start by looking at the function
> gdbarch_init_osabi in gdb/osabi.c to see what it does. In summary, it
> is looking in the list gdb_osabi_handler_list for something that matches
> the argument named info. It only finds a match if the osabi is the same
> and it has an acceptable arch_info (the function can_run_code_for). It
> prints the warning if it doesn't find a match.
>
> The command sequence to start debugging it is something like this:
>
> break gdbarch_init_osabi
> run
>
> It should then stop at the breakpoint, where it is useful to do:
>
> print info
> print *info.bfd_arch_info
> set $tmp=gdb_osabi_handler_list
> while $tmp
> print *$tmp
> print *$tmp->arch_info
> set $tmp=$tmp->next
> end
>
> That might be enough to find why there is no match, but otherwise you
> have to repeatedly use the step command and print other things that the
> code is examining.
>
> __Martin
--
______________________________________________________________________
Dr. Christopher J. Nicol, Phone: (403) 329-2261
University Librarian and FAX: (403) 329-2234
Professor of Economics,
The University of Lethbridge, E-Mail: nicolc@uleth.ca
Lethbridge, Alberta, T1K 3M4, CANADA. http://people.uleth.ca/~nicolc
next prev parent reply other threads:[~2020-05-24 1:55 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 [this message]
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=fde90674-fb5e-14de-7ab1-03d51b7d99ad@uleth.ca \
--to=nicolc@uleth.ca \
--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).