public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@palves.net>
To: Claude Robitaille <claude-robitaille@hotmail.com>,
	Shahab Vahedi <shahab.vahedi@gmail.com>
Cc: Gdb <gdb@sourceware.org>
Subject: Re: Building gdbserver
Date: Mon, 18 Apr 2022 16:38:40 +0100	[thread overview]
Message-ID: <732aabcc-2750-bc38-0fe3-c4e77f93343b@palves.net> (raw)
In-Reply-To: <DS7PR07MB7686B5D95FF3971F61C5BE6DF7F09@DS7PR07MB7686.namprd07.prod.outlook.com>

On 2022-04-17 16:12, Claude Robitaille via Gdb wrote:
> 
> PS
> I took the instruction that I implemented from this wiki page: https://sourceware.org/gdb/wiki/BuildingCrossGDBandGDBserver
> I guess it should be removed or amended to refer to the readme file.
> BuildingCrossGDBandGDBserver - GDB Wiki - sourceware.org<https://sourceware.org/gdb/wiki/BuildingCrossGDBandGDBserver>
> 1. Problem statement "I have a ARM GNU/Linux board, and I want to be able to debug programs running in it, from the comfort of my x86_64 GNU/Linux machine.
> sourceware.org

Thanks for mentioning that this wiki page is what you were following.

This document had been written before gdbserver was moved to the top level, and we didn't remember to update that page.
The gdbserver sources used to live in src/gdb/gdbserver/ up until GDB 10.

I've updated the document now.

Pedro Alves

      parent reply	other threads:[~2022-04-18 15:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17  3:35 Claude Robitaille
2022-04-17 10:23 ` Shahab Vahedi
2022-04-17 15:12   ` Claude Robitaille
2022-04-17 17:19     ` Shahab Vahedi
2022-04-17 18:07       ` Claude Robitaille
2022-04-17 19:40         ` Claude Robitaille
2022-04-18  1:40           ` Claude Robitaille
2022-04-18 15:38     ` Pedro Alves [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=732aabcc-2750-bc38-0fe3-c4e77f93343b@palves.net \
    --to=pedro@palves.net \
    --cc=claude-robitaille@hotmail.com \
    --cc=gdb@sourceware.org \
    --cc=shahab.vahedi@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).