Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Yao Qi <yao@codesourcery.com>
To: Peng Fan <van.freenix@gmail.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: GDB Remote debug: Why several "$Z0,address,length" msg when only set one breakpoint?
Date: Wed, 27 Aug 2014 12:15:00 -0000	[thread overview]
Message-ID: <87d2bmgmil.fsf@codesourcery.com> (raw)
In-Reply-To: <53FD8D31.9010507@gmail.com> (Peng Fan's message of "Wed, 27 Aug	2014 15:48:01 +0800")

Peng Fan <van.freenix@gmail.com> writes:

> 0x87800000 is the entry symbol address of u-boot elf of my platform.
>     1                                                                                 
>     2 u-boot:     file format elf32-littlearm                                         
>     3                                                                                 
>     4                                                                                 
>     5 Disassembly of section .text:                                                   
>     6                                                                                 
>     7 87800000 <__image_copy_start>:                                                  
>     8 87800000: 11 00 00 ea 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5
>     9 87800010: 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5 14 f0 9f e5 

GDB is interested in entry address, but I don't know why GDB insert
breakpoint there.  In GDB, command 'maintenance info breakpoints' can
list all the user breakpoints and internal breakpoints.  If it still
doesn't help, you can debug your gdb, set breakpoint
remote_insert_breakpoint, and check why the breakpoint is inserted at
0x87800000.

-- 
Yao (齐尧)


  reply	other threads:[~2014-08-27 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-26  6:57 Peng Fan
2014-08-26 13:18 ` Luis Machado
2014-08-27  0:36 ` Yao Qi
2014-08-27  7:50   ` Peng Fan
2014-08-27 12:15     ` Yao Qi [this message]
2014-08-27 21:58       ` Pedro Alves
2014-08-28  1:21         ` Peng Fan

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=87d2bmgmil.fsf@codesourcery.com \
    --to=yao@codesourcery.com \
    --cc=gdb@sourceware.org \
    --cc=van.freenix@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