From: Tom Tromey <tromey@redhat.com>
To: Krister Olofsson <krister.olofsson@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: gdb and variadic functions
Date: Tue, 29 Oct 2013 15:09:00 -0000 [thread overview]
Message-ID: <87vc0g8670.fsf@fleche.redhat.com> (raw)
In-Reply-To: <526FCDDB.9090707@gmail.com> (Krister Olofsson's message of "Tue, 29 Oct 2013 16:01:47 +0100")
>>>>> "Krister" == Krister Olofsson <krister.olofsson@gmail.com> writes:
Krister> Building with -gstabs results in wrong value of argc and building with
Krister> -fvar-tracking gives wrong values of arguments in variadic functions.
It's better not to use stabs.
Krister> gcc version 4.2.1 20070719 [FreeBSD]
Krister> GNU gdb 6.1.1 [FreeBSD]
You're using an old version of gcc and an amazingly old version of gdb.
Using more current versions makes your test case work for me. So the
simple answer is that you are probably seeing a bug that was fixed
sometime in the last 6 years (gcc) or 9 years (gdb).
Offhand I don't know what the bug might be.
Tom
next prev parent reply other threads:[~2013-10-29 15:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-29 15:01 Krister Olofsson
2013-10-29 15:09 ` Tom Tromey [this message]
2013-10-29 15:16 ` Krister Olofsson
2013-10-29 19:07 ` Tom Tromey
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=87vc0g8670.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb@sourceware.org \
--cc=krister.olofsson@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