From: Jason R Thorpe <thorpej@wasabisystems.com>
To: Mark Kettenis <kettenis@science.uva.nl>
Cc: gdb@sources.redhat.com
Subject: Re: Anyone using alpha-freebsd target in gdb-current?
Date: Sat, 12 Jan 2002 16:41:00 -0000 [thread overview]
Message-ID: <20020112164126.B542@dr-evil.shagadelic.org> (raw)
In-Reply-To: <s3ivgear3e7.fsf@soliton.wins.uva.nl>; from kettenis@science.uva.nl on Thu, Jan 10, 2002 at 09:55:44AM +0100
On Thu, Jan 10, 2002 at 09:55:44AM +0100, Mark Kettenis wrote:
> I did the port to alpha-freebsd-5.0 (a.k.a. freebsd-current). I still
> work on it from time to time, and it should work reasonably with a
> recent gcc.
Should it also work with GCC 2.95.3?
> The system compiler for freebsd-current generates unusable debug
> output, both for stabs and dwarf2. Gcc 3.0 and above should do much better.
The lossage I'm seeing seems totally irrelavent to debugging symbols,
unfortunately.
> Isn't NetBSD/alpha using ELF? In that case it shouldn't set any
> implicit breakpoints at __start. If NetBSD/alpha doesn't use ELF,
> then you might need to work on getting the old SunOS/a.out shared
> library support working on NetBSD/alpha.
Yes, it's ELF, and it uses solib-svr4.c. I'm referring to
bkpt_names[] in solib-svr4.c:
#define BKPT_AT_SYMBOL 1
#if defined (BKPT_AT_SYMBOL)
static char *bkpt_names[] =
{
#ifdef SOLIB_BKPT_NAME
SOLIB_BKPT_NAME, /* Prefer configured name if it exists. */
#endif
"_start",
"main",
NULL
};
#endif
_start is the executable entry point on FreeBSD/alpha. It's __start on
NetBSD/alpha, and thus my alpha/tm-nbsd.h defines:
#define SOLIB_BKPT_NAME "__start"
As I understand the use of bkpt_names[], it's used to create a solib
event when all of the default shared libraries are loaded for a program.
--
-- Jason R. Thorpe <thorpej@wasabisystems.com>
next prev parent reply other threads:[~2002-01-13 0:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 19:34 Jason R Thorpe
2002-01-10 0:58 ` Mark Kettenis
2002-01-12 16:41 ` Jason R Thorpe [this message]
2002-01-12 16:50 ` Jason R Thorpe
2002-01-17 22:09 ` Jason R Thorpe
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=20020112164126.B542@dr-evil.shagadelic.org \
--to=thorpej@wasabisystems.com \
--cc=gdb@sources.redhat.com \
--cc=kettenis@science.uva.nl \
/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