From: Efim Monyak <ymonyak@lipowsky.de>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb@sources.redhat.com
Subject: Re: restart for remote target
Date: Wed, 26 Jul 2006 13:05:00 -0000 [thread overview]
Message-ID: <44C71BC4.7090005@lipowsky.de> (raw)
In-Reply-To: <20060725174754.GA16907@nevyn.them.org>
Daniel Jacobowitz schrieb:
> On Tue, Jul 25, 2006 at 06:54:09PM +0200, Efim Monyak wrote:
>
>> symbol-file reset.elf
>>
>
> If you want to use symbol files, you're out of luck. When you change
> the symbol file you're going to mess up all your breakpoints.
>
> You might be able to get things to work by not changing the symbol
> file.
>
>
Thanks, without line "symbol-file reset.elf" I have no more error
&"Error in re-setting breakpoint 3:\n"
&"No line 120 in file \"../src/main.c\".\n"
but still
156^error,msg="Warning:\nCannot insert breakpoint 6.\nError
accessing memory add\
ress 0x0: Unknown error 4294967295.\n"
Only after I use "tbreak * 0" ensteed "b * 0" and "delete * 0" it works.
Possibly delete * 0 don't working for GDB with ARM remote target.
I see Z0,0 command to stub after this breakpoint must be deleted
by delete * 0, it is a third breakpoint and it is an error for stub because
only two breakpoints are allowed.
The lines "symbol-file init.elf" and "b end_init" are not changed and
they make no problem. Is the error depend for particular breakpoint type?
I mean breakpoint to address is handled in other way as i.e. breakpoint to
function.
next prev parent reply other threads:[~2006-07-26 7:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-25 15:45 Efim Monyak
2006-07-25 16:01 ` Daniel Jacobowitz
2006-07-25 16:24 ` Efim Monyak
2006-07-25 16:28 ` Daniel Jacobowitz
2006-07-25 17:48 ` Efim Monyak
2006-07-25 18:22 ` Daniel Jacobowitz
2006-07-26 13:05 ` Efim Monyak [this message]
2006-07-26 14:10 ` Daniel Jacobowitz
2006-07-27 13:34 ` Efim Monyak
2006-07-28 15:37 ` Daniel Jacobowitz
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=44C71BC4.7090005@lipowsky.de \
--to=ymonyak@lipowsky.de \
--cc=drow@false.org \
--cc=gdb@sources.redhat.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