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 13:35:15 -0600	[thread overview]
Message-ID: <f5a5c721-19f7-618b-1eb3-ae5205d5fb4b@uleth.ca> (raw)
In-Reply-To: <359bdbb1-c4ab-b89c-6d0a-f18025c64da8@simark.ca>

Simon,

This link:

https://wiki.freebsd.org/201110DevSummit?action=AttachFile&do=get&target=sparc64_status_201110DevSummit.pdf

at page 4, "CPU Type" makes me suspicious that v9 does not correctly 
characterise my processor. In that same document, there is reference to 
support for "UltraSparc, UltraParc III and V9" processors, whereas the 
SunBlade 100 I am using is referenced as having an UltrasSparcIIe 
processor, which is maybe not "v9"? v9 is possibly something else, such 
as UltraSparc III+. There are sparc64-fbsd-nat.o, sparc64-fbsd.tdep.o , 
sparc64-nat.o and sparc64-tdep.o object files in my build directory.


Chris.
On 5/22/2020 12:51 PM, Simon Marchi wrote:
> On 2020-05-22 2:22 p.m., Chris Nicol wrote:
>> 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.
> 
> I'm not really familiar with sparc machines... does that values sound
> good to you?  Does it seem to match the machine you have?
> 
> In any case, that seems to match the osabi registration line in
> sparc64-fbsd-tdep.c:
> 
> gdbarch_register_osabi (bfd_arch_sparc, bfd_mach_sparc_v9, 
> GDB_OSABI_FREEBSD, sparc64fbsd_init_abi);
> 
> Is the file sparc64-fbsd-tdep.c being compiled?  In other words, does
> the file gdb/sparc64-fbsd-tdep.o exist in your build directory?
> 
> Simon
> 



  reply	other threads:[~2020-05-22 19:35 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 [this message]
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=f5a5c721-19f7-618b-1eb3-ae5205d5fb4b@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).