From: Pedro Alves <palves@redhat.com>
To: Luis Machado <lgustavo@codesourcery.com>, gdb-patches@sourceware.org
Cc: simon.marchi@polymtl.ca
Subject: Re: [PATCH,v2] Make language setting tests more robust
Date: Mon, 06 Feb 2017 18:24:00 -0000 [thread overview]
Message-ID: <4dd0f39e-d2db-dbcb-a983-f9c10fd0c0bd@redhat.com> (raw)
In-Reply-To: <40ce75b2-3e49-67b9-94e0-5d55e98ee5f9@codesourcery.com>
On 02/06/2017 06:22 PM, Luis Machado wrote:
> On 02/06/2017 12:08 PM, Pedro Alves wrote:
>> On 02/06/2017 06:04 PM, Luis Machado wrote:
>>
>>> That returns language_asm for me. Supposedly because gdb has seen asm
>>> from glibc and then sticked with it when it reached the test program's
>>> main. And the program has no debug info.
>>
>> No, I don't think that is why. What sticks is "current_language", not
>> the frame's language.
>
> True. gdb is still seeing asm for the frame with main though. But that
> sounds like an expected outcome.
Why? Where is GDB retrieving that from? Did you step through
get_frame_language?
Thanks,
Pedro Alves
next prev parent reply other threads:[~2017-02-06 18:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 15:17 [PATCH] " Luis Machado
2017-02-01 18:38 ` Simon Marchi
2017-02-01 19:22 ` Luis Machado
2017-02-01 19:25 ` Simon Marchi
2017-02-01 21:50 ` Keith Seitz
2017-02-01 23:29 ` Luis Machado
2017-02-02 1:24 ` Simon Marchi
2017-02-01 20:21 ` [PATCH,v2] " Luis Machado
2017-02-02 1:33 ` Simon Marchi
2017-02-03 0:37 ` Pedro Alves
2017-02-06 14:54 ` Luis Machado
2017-02-06 15:09 ` Luis Machado
2017-02-06 16:51 ` Pedro Alves
2017-02-06 18:04 ` Luis Machado
2017-02-06 18:08 ` Pedro Alves
2017-02-06 18:22 ` Luis Machado
2017-02-06 18:24 ` Pedro Alves [this message]
2017-02-06 19:56 ` Luis Machado
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=4dd0f39e-d2db-dbcb-a983-f9c10fd0c0bd@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=lgustavo@codesourcery.com \
--cc=simon.marchi@polymtl.ca \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).