From: "Petr Hluzín" <petr.hluzin@gmail.com>
To: G <tjmadwja@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Debugging variable arguments functions (stdarg)
Date: Fri, 16 Jul 2010 18:58:00 -0000 [thread overview]
Message-ID: <AANLkTikrVS4Ol194JZ2PQHKW3at02HEZxE495BEDFXds@mail.gmail.com> (raw)
In-Reply-To: <AANLkTiknIhu1S37em4tWKFEocYpTSxtwyDBmslmrSOOo@mail.gmail.com>
On 15 July 2010 17:47, G <tjmadwja@gmail.com> wrote:
> Hello,
>
> How can I look at the values of "..." in a function which can
> take a variable number of arguments (i.e. uses va_start(),
> va_end() etc.) in gdb?
There is no nice way to do that. GCC does not record the actual types
used in a call site of a variadic function, e.g. what is on the
call-site of WriteLog(int,int,char*,...) in MysqlWrapper.
Workaround A:
Alter source code of the caller to:
const char * msg = mysql_error(sql_handle)
WriteLog(stuff1,stuff1,stuff3, query, msg);
and hope the compiler does not optimize the local variable.
Workaround B:
Get value of stack pointer (RSP?) of frame MysqlWrapper() and dump raw
memory around the address. You should see these values somewhere
around:
0x00000000004041e2 (return address in MysqlWrapper)
0x406bf0 (the third argument to WriteLog)
Between these two values should be the values of 3rd and 4th argument.
(You have to cast them to char*.)
--
Petr Hluzin
next prev parent reply other threads:[~2010-07-16 18:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-15 15:47 G
2010-07-16 18:57 ` Michael Snyder
2010-07-16 18:58 ` Petr Hluzín [this message]
2010-07-16 19:12 ` Jan Kratochvil
2010-07-18 19:28 ` Petr Hluzín
2010-07-19 14:19 ` G
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=AANLkTikrVS4Ol194JZ2PQHKW3at02HEZxE495BEDFXds@mail.gmail.com \
--to=petr.hluzin@gmail.com \
--cc=gdb@sourceware.org \
--cc=tjmadwja@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