From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: gdb@sourceware.org
Subject: Re: Strange backtrace from GDB 7.5.91
Date: Wed, 20 Mar 2013 17:58:00 -0000 [thread overview]
Message-ID: <20130320175740.GA31878@host2.jankratochvil.net> (raw)
In-Reply-To: <83ppyuynhd.fsf@gnu.org>
On Wed, 20 Mar 2013 18:45:02 +0100, Eli Zaretskii wrote:
> #0 relocate_path (flag=1, initial=0x71a51b "d:/usr/share/gdb",
> progname=0x260ed0 "d:\\usr\\eli\\utils\\gdb-7.5.91\\gdb\\gdb.exe")
> at main.c:124
> #1 relocate_gdb_directory (
> initial=initial@entry=0x71a51b "d:/usr/share/gdb", flag=flag@entry=1)
> at main.c:124
[...]
> But relocate_path's argument list is this:
>
> relocate_path (const char *progname, const char *initial, int flag)
>
> i.e., the FLAG argument is the last one, not the first one.
It needs a fix in GDB:
Bug 15223 - reversed order of inlined function parameters
http://sourceware.org/bugzilla/show_bug.cgi?id=15223
> #0 relocate_path (initial=0x71a51b "d:/usr/share/gdb",
> progname=0x260ed0 "d:\\usr\\eli\\utils\\gdb-7.5.91\\gdb\\gdb.exe",
> flag=<optimized out>) at main.c:109
> #1 relocate_path (flag=1, initial=0x71a51b "d:/usr/share/gdb",
> progname=0x260ed0 "d:\\usr\\eli\\utils\\gdb-7.5.91\\gdb\\gdb.exe")
> at main.c:120
> #2 relocate_gdb_directory (
> initial=initial@entry=0x71a51b "d:/usr/share/gdb", flag=flag@entry=1)
> at main.c:124
> #3 0x004f0b1d in captured_main (data=data@entry=0x572ff10) at main.c:399
>
> Is this due to inlining or something? Is this a bug?
Probably all the frames #0..#2 are inlined, see "info frame". It is not a bug
a single function is there multiple times, GCC does so.
Jan
next prev parent reply other threads:[~2013-03-20 17:58 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 17:45 Eli Zaretskii
2013-03-20 17:58 ` Jan Kratochvil [this message]
2013-03-20 18:04 ` Eli Zaretskii
2013-03-20 18:07 ` Jan Kratochvil
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=20130320175740.GA31878@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=eliz@gnu.org \
--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