Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Yao Qi <qiyaoltc@gmail.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: GDB Patches <gdb-patches@sourceware.org>
Subject: Re: [PATCH 2/2] Fix gdb.mi/mi-stack.exp when gcc generates a stack protector
Date: Tue, 02 Jan 2018 10:38:00 -0000	[thread overview]
Message-ID: <CAH=s-POVUgp0Vbh_g6bchswwL8UfPy2XSZmBB2ONKUb4A1Xe7w@mail.gmail.com> (raw)
In-Reply-To: <20171216145651.13936-2-simon.marchi@polymtl.ca>

On Sat, Dec 16, 2017 at 2:56 PM, Simon Marchi <simon.marchi@polymtl.ca> wrote:
> I see some failures in the gdb.mi/mi-stack.exp test.  The test runs to
> the callee4 function:
>
>   int callee4 (void)
>   {
>     int A=1;
>     int B=2;
>     int C;
>     int D[3] = {0, 1, 2};
>
>     C = A + B;
>     return 0;
>   }
>
> and expects to be stopped at the A=1 line.  However, when gcc generates
> some stack protection code, it will stop at the { instead, as shown by
> this disassembly (after I did "break callee4" and "run"):

Can't we fix GDB to skip these stack protection code?

-- 
Yao (齐尧)


  reply	other threads:[~2018-01-02 10:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-16 14:57 [PATCH 1/2] Fix indentation in gdb.mi/mi-stack.exp Simon Marchi
2017-12-16 14:57 ` [PATCH 2/2] Fix gdb.mi/mi-stack.exp when gcc generates a stack protector Simon Marchi
2018-01-02 10:38   ` Yao Qi [this message]
2018-01-02 18:14     ` Simon Marchi
2018-01-03 21:53       ` Yao Qi
2018-01-03 22:39         ` Simon Marchi
2018-01-04 20:10           ` Simon Marchi
2018-04-07 18:14         ` Simon Marchi

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='CAH=s-POVUgp0Vbh_g6bchswwL8UfPy2XSZmBB2ONKUb4A1Xe7w@mail.gmail.com' \
    --to=qiyaoltc@gmail.com \
    --cc=gdb-patches@sourceware.org \
    --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