Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: kew@emc.com
To: gdb@sourceware.org
Subject: STABS records for 64-bit function arguments via registers in i386
Date: Wed, 13 Oct 2010 15:19:00 -0000	[thread overview]
Message-ID: <4CB5CB63.5020901@emc.com> (raw)

Hi

In i386 architecture (32 bit) gcc can optimize a static function to pass 
function arguments via registers (instead of in the stack). For 64-bit 
arguments, it uses 2 registers, but gdb reports only 1 (via "info 
scope") when the binary being debugged is compiled using the STABS 
debugging format.

I checked using objdump and could see indeed only 1 N_RSYM record being 
given (so no wonder gdb would only report 1 register).

How does the STABS debugging format indicate the 2 registers used for 
passing 64 function arguments in i386 architecture? Is this supported? 
If not, what's the process to add support for it?

If this is not the right mailing list to ask this question, sorry and 
please if you could refer me to the right mailing list, I'd appreciate it.

Thanks
Andrew


             reply	other threads:[~2010-10-13 15:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-13 15:19 kew [this message]
2010-10-13 16:07 ` 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=4CB5CB63.5020901@emc.com \
    --to=kew@emc.com \
    --cc=gdb@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