Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Randolph Chung <randolph@tausq.org>
To: gdb-patches@sources.redhat.com
Subject: Re: [rfc/rfa] Dummy calls for hppa-hpux
Date: Wed, 15 Dec 2004 22:46:00 -0000	[thread overview]
Message-ID: <20041215214833.GF29171@tausq.org> (raw)
In-Reply-To: <20041213172952.GO29171@tausq.org>

> hppa64-hp-hpux11.11
> # of expected passes            35
> # of unexpected failures        64
> # of known failures             3
> 
> the large number of failures in hppa64-hp-hpux11.11 are due to a
> cascading failure early on in the test (we have some problems passing
> function pointers into functions); however, since basic infcalls work
> now, i suspect a much larger portion of gdb testcases will benefit.

i've looked into these failures a bit further; hppa64 requires indirect
function calls to be made via function descriptors (on hppa32, it can be
made via either a function descriptor or a "straight" function pointer).
when doing a call like "p t_func_values (func_val1, add)" where
"func_val1" is a function pointer variable, and "add" is a local
function, gdb seems to be passing a function descriptor value for
"func_val1", but a regular pointer for "add". When t_func_values tries
to call the corresponding functions, it fails because it tries to
dereference the function pointer as a function descriptor.

I haven't been able to determine where and how gdb resolves the value of
"add" to pass to call_functions_by_hand (). any hints would be
appreciated.

btw, for this hpux dummy calls patch, if i don't get any other comments
i'll check it in tomorrow. :)

randolph
-- 
Randolph Chung
Debian GNU/Linux Developer, hppa/ia64 ports
http://www.tausq.org/


      reply	other threads:[~2004-12-15 21:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-13 17:39 Randolph Chung
2004-12-15 22:46 ` Randolph Chung [this message]

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=20041215214833.GF29171@tausq.org \
    --to=randolph@tausq.org \
    --cc=gdb-patches@sources.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