public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Chris Nicol <nicolc@uleth.ca>
To: Simon Marchi <simark@simark.ca>, gdb@sourceware.org
Subject: Re: gdb 8.3: "handler for the OSI ABI "FreeBSD" is not built into this configuration"
Date: Fri, 22 May 2020 12:22:42 -0600	[thread overview]
Message-ID: <d39012d4-0942-8022-e7d2-1e0d9087595b@uleth.ca> (raw)
In-Reply-To: <04509e3f-e5d9-72fb-1b1a-6d58a08482a2@simark.ca>

Dear Simon,

Thanks for your reply. I went ahead and completed the build of gbd-9.1, 
which had been the original plan. With the gdb-9.1 executable, I re-ran 
it against the llvm-tblgen binary and its core dump, with the same 
result as in gdb-8.3. So this is progress of a sort, I suppose.

Taking now the gdb-9.1 and loading gcc9 into the debugger, then "show 
architecture" yields "The target architecture is set automatically 
(currently sparc:v9)". The system I am using is based on the 500-MHz 
UltraSPARC IIe processor. So maybe this setting, sparc:v9, is wrong for 
this platform?

Best wishes,

Chris.

On 5/22/2020 11:36 AM, Simon Marchi wrote:
> On 2020-05-22 1:56 a.m., Chris Nicol wrote:
>> Dear List,
>>
>> My system - SunBlade 100 running FreeBSD 12.1 had a stock gdb 6.1.1
>> version of the debugger, which came with the FreeBSD 12.1 I am running. This version would not 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".
> 
> Let's start with this, as it's a sign that there's probably something wrong
> already.
> 
> There should be a call to gdbarch_register_osabi that registers a handler
> for the (cpu, os) pair.  In sparc64-fbsd-tdep.c, I see this call, for
> example:
> 
>     gdbarch_register_osabi (bfd_arch_sparc, bfd_mach_sparc_v9,
>                             GDB_OSABI_FREEBSD, sparc64fbsd_init_abi);
> 
> 
> However, maybe your particular machine does not match the machine
> bfd_arch_sparc / bfd_mach_sparc_v9?  What does it show if you load
> some binary file into GDB, then do "show architecture"?
> 
> Simon
> 


-- 
______________________________________________________________________
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

  reply	other threads:[~2020-05-22 18:22 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 [this message]
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=d39012d4-0942-8022-e7d2-1e0d9087595b@uleth.ca \
    --to=nicolc@uleth.ca \
    --cc=gdb@sourceware.org \
    --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).