Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@act-europe.fr>
To: Nick Duffek <nsd@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: patch to gdb on Tru64 5.1
Date: Thu, 10 May 2001 17:06:00 -0000	[thread overview]
Message-ID: <20010511020554.I15086@act-europe.fr> (raw)
In-Reply-To: <200105101706.f4AH6aC13735@rtl.cygnus.com>

> >alpha-nat.c:
> >------------
> >fetch_osf_core_registers: adapt the table used to map the regnum to
> > the core register section index to work on Tru64 5.1 as well.
> 
> I did that slightly differently:

Thanks for you suggestion. However, I tried your change, but then I
could not build gdb on Dec Unix 4.0f...

> >alpha-osf5.mh:
> >--------------
> >new file. This is a modified version of alpha-osf3.mh where
> > -DUSE_LDR_ROUTINES is added to the compilation flags. This forces gdb to
> > use the xproc library to load the symbols, instead of relying on an
> > empirical algorithm (which does not work on Tru64 5.1 anymore).
> 
> That didn't work when I tried it, because the xproc routines only allow a
> process to examine itself.  It _seems_ to work because GDB happens to load
> the same shared libraries as most programs it debugs (libc.so and
> libm.so), but it doesn't when debugging programs linked against other
> shared libs.
> 
> I'll post an alternative patch for shared library support in a separate
> message.

I am looking forward to it.

-- 
Joel


  reply	other threads:[~2001-05-10 17:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-08 23:22 Joel Brobecker
2001-05-09  7:41 ` Christopher Faylor
2001-05-09 10:57   ` Joel Brobecker
2001-05-09 13:56     ` Christopher Faylor
2001-05-10  8:32   ` Andrew Cagney
2001-05-09 11:07 ` Jim Blandy
2001-05-10  8:32 ` Andrew Cagney
2001-05-10 17:03   ` Joel Brobecker
2001-05-11 15:29     ` Andrew Cagney
2001-05-12 19:30       ` Nick Duffek
2001-05-10  9:56 ` Nick Duffek
2001-05-10 17:06   ` Joel Brobecker [this message]
2001-05-10 17:20     ` Nick Duffek

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=20010511020554.I15086@act-europe.fr \
    --to=brobecker@act-europe.fr \
    --cc=gdb-patches@sources.redhat.com \
    --cc=nsd@redhat.com \
    /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