Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Doug Evans <xdje42@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] testsuite/boards/stabs.exp
Date: Mon, 15 Dec 2014 03:23:00 -0000	[thread overview]
Message-ID: <8761ddvbp6.fsf@codesourcery.com> (raw)
In-Reply-To: <CAP9bCMRKtavAVZRjk67PO6k-Zzd34VAGuF-q5tr600wG4TNYow@mail.gmail.com>	(Doug Evans's message of "Sat, 13 Dec 2014 23:05:16 -0800")

Doug Evans <xdje42@gmail.com> writes:

> b) The testsuite gets the -g* variant to use from the debug_flags board config.
> If you specify CFLAGS_FOR_TARGET then that value *and* the
> debug_flags board config are passed to gcc.
> Plus, -g -gstabs != -gstabs -g.
> [I didn't dig into why, easy enough if it becomes important.]

Oh, it is surprise to me.

> The high order bit is that the right way to specify the flag
> to control the debug format is with the debug_flags board config.
>
> The difference can be seen by trying both.
> A simple example to play with is gdb.cp/bool.exp.
>
> check-gdb --target_board=stabs bool.exp
> -> 2 fails
> FAIL: gdb.cp/bool.exp: print return_true()
> FAIL: gdb.cp/bool.exp: print return_false()
>
> check-gdb CFLAGS_FOR_TARGET=-gstabs bool.exp
> -> 2 passes

Thanks for giving this example.

>
> Is there something about adding a board file that causes problems I'm
> not aware of?
> If so, we'd better establish what it is and get it written down.
> I can imagine wanting more board files.  :-)

Adding board file stabs.exp is fine to me.

-- 
Yao (齐尧)


  parent reply	other threads:[~2014-12-15  3:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-13 23:46 Doug Evans
2014-12-14  6:42 ` Yao Qi
2014-12-14  7:05   ` Doug Evans
2014-12-14 13:24     ` Joel Brobecker
2014-12-15  3:23     ` Yao Qi [this message]
2014-12-15 11:12     ` Pedro Alves
2014-12-17  7:28       ` Doug Evans
2014-12-14 13:20   ` Joel Brobecker
2014-12-14 17:23     ` Doug Evans

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=8761ddvbp6.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@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