From: Daniel Jacobowitz <drow@false.org>
To: Randolph Chung <randolph@tausq.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [RFA] solib-som.c fix for hpux
Date: Fri, 24 Mar 2006 21:07:00 -0000 [thread overview]
Message-ID: <20060324202315.GB26748@nevyn.them.org> (raw)
In-Reply-To: <442382D1.4010104@tausq.org>
On Fri, Mar 24, 2006 at 01:25:37PM +0800, Randolph Chung wrote:
> Dan J's change to solib handling
> (http://sources.redhat.com/ml/gdb-patches/2006-01/msg00198.html) exposed
> a probably unfounded assumption in the SOM solib code that assumes that
> the solib_create_inferior_hook will always be called before current_sos.
> As a result, gdb cvs on HPUX 32-bit would always error out when trying
> to run any executable with the message "Debugging dynamic executables
> loaded via the hpux8 dld.sl is not supported.". The most straightforward
> fix is to remove the error and handle the case where there is not yet a
> link map; that is what I have in the patch below. OTOH this does remove
> the error message if anybody does try to run gdb on hpux8 (!!!)
Grr! I tried to catch all of these. Some assume that add is called
first... others assume that create is called first...
> 2006-03-24 Randolph Chung <tausq@debian.org>
>
> * solib-som.c (link_map_start): Don't error out if there is
> not yet a link map.
It seems OK to me, but I don't want to approve SOM changes; maybe get
Kevin's opinion, since this is a shared library topic?
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2006-03-24 20:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 9:38 Randolph Chung
2006-03-24 21:07 ` Daniel Jacobowitz [this message]
2006-03-25 17:46 ` Randolph Chung
2006-03-28 0:00 ` Kevin Buettner
2006-03-28 18:29 ` Randolph Chung
2006-03-24 23:17 ` Mark Kettenis
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=20060324202315.GB26748@nevyn.them.org \
--to=drow@false.org \
--cc=gdb-patches@sources.redhat.com \
--cc=randolph@tausq.org \
/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