From: Mike Frysinger <vapier@gentoo.org>
To: gdb@sourceware.org
Cc: Mathias Lafeldt <misfire@debugon.org>
Subject: Re: Remote debugging w/o symbols
Date: Thu, 01 Jul 2010 17:00:00 -0000 [thread overview]
Message-ID: <201007011259.12422.vapier@gentoo.org> (raw)
In-Reply-To: <4C2C7E02.5050007@debugon.org>
[-- Attachment #1: Type: Text/Plain, Size: 760 bytes --]
On Thursday, July 01, 2010 07:37:38 Mathias Lafeldt wrote:
> is there any way I can do remote debugging without using a command like
> "file" to get the symbols?
>
> After running "target remote ..." to connect to a remote stub, "dump" or
> "disassemble" fail due to a memory access error. I know that the symbols
> are required for source-level debugging, but I guess there still must be
> a way to dump memory and disassemble it without them.
>
> Manually defining memory regions with "mem" didn't change the situation.
you need to show the actual commands you're running and the output you're
seeing. i do remote debugging with no symbols all the time and dont have
problems reading/writing/disassembling random pieces of memory.
-mike
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2010-07-01 17:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 11:37 Mathias Lafeldt
2010-07-01 17:00 ` Mike Frysinger [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=201007011259.12422.vapier@gentoo.org \
--to=vapier@gentoo.org \
--cc=gdb@sourceware.org \
--cc=misfire@debugon.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