From: Hans-Peter Nilsson <hp@bitrange.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org, hp@axis.com
Subject: Re: [PATCH] sim: gdbinit: hoist setup to common code
Date: Mon, 21 Feb 2022 22:09:39 -0500 (EST) [thread overview]
Message-ID: <alpine.BSF.2.20.16.2202212206050.42702@arjuna.pair.com> (raw)
In-Reply-To: <20220217054035.10127-1-vapier@gentoo.org>
On Thu, 17 Feb 2022, Mike Frysinger via Gdb-patches wrote:
> This was left in subdirs because of the dynamic cgen usage. However,
> we can move this breakpoint call to runtime and let gdb detect whether
> the symbol exists.
The .gdbinit file doesn't do much good in the sim/ directory
instead of sim/<subdir> where the "run" program is located (such
that .gdbinit is loaded when you start gdb there to debug it).
Make a symlink in sim/<subdir>?
brgds, H-P
next prev parent reply other threads:[~2022-02-22 3:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 5:40 Mike Frysinger
2022-02-22 3:09 ` Hans-Peter Nilsson [this message]
2022-02-22 3:29 ` Mike Frysinger
2022-02-22 3:36 ` [PATCH] sim: add arch/.gdbinit stub scripts Mike Frysinger
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=alpine.BSF.2.20.16.2202212206050.42702@arjuna.pair.com \
--to=hp@bitrange.com \
--cc=gdb-patches@sourceware.org \
--cc=hp@axis.com \
--cc=vapier@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).