Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Thomas Schwinge <thomas@codesourcery.com>
To: Joel Brobecker <brobecker@adacore.com>, Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, cltang@codesourcery.com
Subject: Re: [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p
Date: Tue, 15 May 2012 15:35:00 -0000	[thread overview]
Message-ID: <87havhsbib.fsf@schwinge.name> (raw)
In-Reply-To: <20120510212054.GA5886@adacore.com>

[-- Attachment #1: Type: text/plain, Size: 1225 bytes --]

Hi!

On Thu, 10 May 2012 14:20:54 -0700, Joel Brobecker <brobecker@adacore.com> wrote:
> > Agreed.  I stared at these debug info for a while, but unable to have
> > a clue on heuristics.  My feeling is that these debug info doesn't give
> > us more than what source code can give, but the heuristics we are looking
> > for are about the difference on different targets, given the same source.
> > That is to say, on different targets, although the number of parameters
> > is different, the debug info is almost the same and hard to get heuristics,
> 
> Can we use the fact that functions that have their first parameter
> be a nameless, artificial, paramter whose type is a pointer to
> the return type? Or would this heuristics trigger in other situations?

Just a quick thought without having a lot of context on this issue --
what about the case where there isn't even any debug information
available for the function to be called?  Does this rule out the DWARF
route, or isn't that something to be prepared for?

> If that doesn't work, then I am running out of ideas, and then we'll
> have to start looking giving GDB insider knowledge. But I really don't
> like that idea.


Grüße,
 Thomas

[-- Attachment #2: Type: application/pgp-signature, Size: 489 bytes --]

  parent reply	other threads:[~2012-05-15 15:35 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-18 13:28 Yao Qi
2012-04-18 13:18 ` [PATCH 2/4] tic6x: Install return_with_first_hidden_param_p Yao Qi
2012-05-16 20:59   ` Tom Tromey
2012-04-18 13:18 ` [PATCH 3/4] sh: " Yao Qi
2012-05-16 21:00   ` Tom Tromey
2012-04-18 13:18 ` [PATCH 4/4] m68k: " Yao Qi
2012-05-16 21:01   ` Tom Tromey
2012-04-25 11:02 ` [PATCH 1/4] New gdb arch hook: return_with_first_hidden_param_p Yao Qi
2012-05-03  0:43 ` [ping 2] : " Yao Qi
2012-05-03  1:15 ` Joel Brobecker
2012-05-03  7:00   ` Yao Qi
2012-05-04 17:58     ` Joel Brobecker
2012-05-07  3:39       ` Yao Qi
2012-05-07 20:14         ` Joel Brobecker
2012-05-09  8:39           ` Yao Qi
2012-05-10 21:21             ` Joel Brobecker
2012-05-11 10:35               ` Yao Qi
2012-05-14 17:15                 ` Joel Brobecker
2012-05-15  6:51                   ` Yao Qi
2012-05-15 15:01                     ` Joel Brobecker
2012-05-16  1:37                       ` Yao Qi
2012-05-16 15:31                         ` Joel Brobecker
2012-05-16 21:03                           ` Tom Tromey
2012-05-15 18:03                     ` Mark Kettenis
2012-05-16  1:55                       ` Yao Qi
2012-05-17 21:02                         ` Mark Kettenis
2012-07-06 13:17                       ` Gary Benson
2012-05-15 15:35               ` Thomas Schwinge [this message]
2012-05-15 21:30                 ` Joel Brobecker
2012-05-03 14:04   ` Chung-Lin Tang
2012-05-16 20:56 ` Tom Tromey
2012-05-16 23:03   ` Mark Kettenis
2012-06-08 14:30     ` Yao Qi

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=87havhsbib.fsf@schwinge.name \
    --to=thomas@codesourcery.com \
    --cc=brobecker@adacore.com \
    --cc=cltang@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=yao@codesourcery.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