Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: gdb-patches@sourceware.org
Subject: [committed] [patch, testsuite] Set language after reaching to main function
Date: Fri, 05 Aug 2011 09:45:00 -0000	[thread overview]
Message-ID: <4E3BBB7B.5020204@codesourcery.com> (raw)
In-Reply-To: <201108041032.27014.pedro@codesourcery.com>

On 08/04/2011 05:32 PM, Pedro Alves wrote:
> On Thursday 04 August 2011 04:10:35, Yao Qi wrote:
>> I find some similar failures below when I examine gdb test result,
>>
>>   FAIL: gdb.cp/cplusfuncs.exp: set language c++
>>   FAIL: gdb.cp/inherit.exp: set language c++
>>   FAIL: gdb.base/callfuncs.exp: set language c
>>
>> They are all caused by warning emitted by gdb "Warning: the current
>> language does not match this frame.".  I examined the frame like this:
>>
>> (gdb) info frame
>> Stack level 0, frame at 0x40017780:
>>  pc = 0x40000000 in _reset_ram
>>     (reset-ram.S:24);
>>     saved pc 0x40000a5c
>>  source language asm.
>>  Arglist at 0x40017780, args:
>>  Locals at 0x40017780, Previous frame's sp is 0x40017780
>>
>> My gdb is working with bare-mental board, and start up code is written
>> in assembly.  That is the reason why gdb emit such warning when we set
>> language while pc is still within assembly code.
>>
>> This patch is to address this problem by moving "set language" after
>> program hits breakpoint on main.
>>
>> OK?
> 
> Makes sense to me.  Okay.
> 

Thanks for the review.  Committed.
http://sourceware.org/ml/gdb-cvs/2011-08/msg00028.html

-- 
Yao (齐尧)


      reply	other threads:[~2011-08-05  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-04  3:11 Yao Qi
2011-08-04  9:32 ` Pedro Alves
2011-08-05  9:45   ` Yao Qi [this message]

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=4E3BBB7B.5020204@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@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