public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Shahab Vahedi <Shahab.Vahedi@synopsys.com>
To: Yuriy Kolerov <kolerov93@gmail.com>
Cc: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>,
	Shahab Vahedi <Shahab.Vahedi@synopsys.com>
Subject: Re: [PATCH] arc: Don't build arc-analyze-prologue.S with -g
Date: Tue, 27 Feb 2024 14:03:20 +0000	[thread overview]
Message-ID: <aa7f6c6e-ea08-40a1-8bc2-1a260f77d084@synopsys.com> (raw)
In-Reply-To: <20240222080219.51830-1-kolerov93@gmail.com>

On 2/22/24 09:02, Yuriy Kolerov wrote:
> arc-analyze-prologue.S test does not contain debug information thus
> it must be compiled without -g option. Otherwise GDB will try to
> unwind frames using debug information (which does not exist for .S
> code!) instead of analyzing frames manually.
> 
> Signed-off-by: Yuriy Kolerov <kolerov93@gmail.com>
> ---
>  gdb/testsuite/gdb.arch/arc-analyze-prologue.exp | 8 +++++++-
>  1 file changed, 7 insertions(+), 1 deletion(-)

Approved-By: Shahab Vahedi <shahab@synopsys.com>



  reply	other threads:[~2024-02-27 14:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-22  8:02 Yuriy Kolerov
2024-02-27 14:03 ` Shahab Vahedi [this message]
2024-02-27 14:12 ` [PUSHED] " Shahab Vahedi

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=aa7f6c6e-ea08-40a1-8bc2-1a260f77d084@synopsys.com \
    --to=shahab.vahedi@synopsys.com \
    --cc=gdb-patches@sourceware.org \
    --cc=kolerov93@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).