Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@specifix.com>
To: Pavel Chernikov <pchernik@gmail.com>
Cc: Joel Brobecker <brobecker@adacore.com>, gdb@sourceware.org
Subject: Re: gdb / dbx / pstack question - getting function argument 	addresses from stack
Date: Thu, 26 Jun 2008 19:11:00 -0000	[thread overview]
Message-ID: <1214507487.3601.1387.camel@localhost.localdomain> (raw)
In-Reply-To: <7611a2ff0806261156x3b6dd54cv880129c0be194e06@mail.gmail.com>

On Thu, 2008-06-26 at 14:56 -0400, Pavel Chernikov wrote:
> Right, understood - thanks for pointing that out to me. I should have
> mentioned that the original platform was SPARC Solaris and the new
> platform is I386 Linux.
> 
> With that said, am I absolutely-totally-100% out of luck with being
> able to find function argument addresses? Or is there some way of
> doing this?

The key constraint is "without debug info".

Under that constraint you are pretty much out of luck.


> Ideally, I'd like to write the following solution in C:
> * List all function calls with corresponding function argument list
> for each function

That's exactly what debug info is for.
With modern compiler abis and complex architectures
like Intel, it's nominally-close-to-impossible
to do that without debug info.




  parent reply	other threads:[~2008-06-26 19:11 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-26 13:20 Pavel Chernikov
2008-06-26 14:26 ` Joel Brobecker
2008-06-26 15:03   ` Pavel Chernikov
2008-06-26 16:25     ` Joel Brobecker
2008-06-26 18:09       ` Pavel Chernikov
2008-06-26 18:47         ` Michael Snyder
2008-06-26 18:57           ` Pavel Chernikov
2008-06-26 19:04             ` Daniel Jacobowitz
2008-06-26 19:06             ` Joel Brobecker
2008-06-26 19:11             ` Michael Snyder [this message]
2008-06-26 18:50         ` Joel Brobecker
2008-06-26 19:01           ` Pavel Chernikov
2008-06-26 19:07           ` Michael Snyder

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=1214507487.3601.1387.camel@localhost.localdomain \
    --to=msnyder@specifix.com \
    --cc=brobecker@adacore.com \
    --cc=gdb@sourceware.org \
    --cc=pchernik@gmail.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