public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "ssbssa at yahoo dot de" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug c++/15559] Method call and calling convention
Date: Thu, 27 Feb 2014 19:02:00 -0000	[thread overview]
Message-ID: <bug-15559-4717-r09MWUpgvF@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15559-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=15559

--- Comment #15 from Domani Hannes <ssbssa at yahoo dot de> ---
Hello asmwarrior

Yes, looks like my strategy doesn't work in every situation.
find_pc_function() can fail (maybe because of some missing debug information?),
then it just stops looking.
A minimal_symbol would still be available, but it's not really useful for this
situation.

I looked at your code again as well.
find_pc_symtab(find_function_addr(function,NULL)) would work as well, so we
don't need that global i386_windows_build_gt_gcc46.

But I found no way to locally find out if it's a static function.
There is function->type->main_type->flag_static, but it's always 0 (and as far
as I can tell not used).

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2014-02-27 19:02 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-01 19:48 [Bug c++/15559] New: " kifathegreat at gmail dot com
2013-10-05 14:32 ` [Bug c++/15559] " asmwarrior at gmail dot com
2013-10-05 14:55 ` asmwarrior at gmail dot com
2013-10-05 15:46 ` asmwarrior at gmail dot com
2013-10-08  4:01 ` asmwarrior at gmail dot com
2013-10-08  6:19 ` asmwarrior at gmail dot com
2013-10-08 11:13 ` asmwarrior at gmail dot com
2013-10-08 13:13 ` xunxun1982 at gmail dot com
2013-10-08 15:28 ` asmwarrior at gmail dot com
2013-10-09  6:59 ` asmwarrior at gmail dot com
2013-12-09 15:15 ` i.nixman at gmail dot com
2013-12-10  7:14 ` i.nixman at autistici dot org
2013-12-10  7:59 ` asmwarrior at gmail dot com
2014-02-25 11:20 ` ssbssa at yahoo dot de
2014-02-25 20:12 ` ssbssa at yahoo dot de
2014-02-26  4:28 ` asmwarrior at gmail dot com
2014-02-26 20:24 ` ssbssa at yahoo dot de
2014-02-27 15:22 ` asmwarrior at gmail dot com
2014-02-27 19:02 ` ssbssa at yahoo dot de [this message]
2014-03-01 14:23 ` asmwarrior at gmail dot com
2014-03-01 14:29 ` asmwarrior at gmail dot com
2014-03-26 14:32 ` julian at codesourcery dot com
2020-04-30 12:37 ` cvs-commit at gcc dot gnu.org
2020-04-30 12:38 ` ssbssa at sourceware dot org
2020-04-30 14:57 ` asmwarrior at gmail dot com

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=bug-15559-4717-r09MWUpgvF@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).