Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Anmol P. Paralkar" <anmol@freescale.com>
To: gdb@sourceware.org
Subject: Cannot insert breakpoint -1.
Date: Fri, 24 Jul 2009 21:12:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.64.0907241042280.31686@lds03-tx32> (raw)

Hello,

  Is there a reason why GDB will try to set a breakpoint (breakpoint number: -1) at
  the entry point address on a 'c', after a 'target remote'? (I am using a GDB stub
  at the remote end that resides in a hypervisor upon which guest OS'es run).

  I am using gdb-6.8.50.20090717; but, I suppose that this is general GDB behaviour.

--------------------------------------------------------------------------------
  (gdb) target remote :12007
Remote debugging using :12007
warning: Loadable segment "cpu0_heap_stack" outside of ELF segments
warning: Loadable segment "cpu1_heap_stack" outside of ELF segments
warning: Loadable segment "cpu2_heap_stack" outside of ELF segments
warning: Loadable segment "cpu3_heap_stack" outside of ELF segments
warning: Loadable segment "cpu4_heap_stack" outside of ELF segments
warning: Loadable segment "cpu5_heap_stack" outside of ELF segments
warning: Loadable segment "cpu6_heap_stack" outside of ELF segments
warning: Loadable segment ".stats_heap" outside of ELF segments
warning: Loadable segment ".dpa_mem" outside of ELF segments
0x0013c880 in ?? ()
(gdb) p $pc
$1 = (void (*)()) 0x13c880
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint -1.
Error accessing memory address 0x110000: Unknown error 18446744073709551615.
--------------------------------------------------------------------------------

  (The entry point is likely not mapped into the TLB at that stage and so it is
  really a visible problem, else it just does this silently without it getting
  any attention).

  I tried to work around the issue by using set remote-<name>-packet, where <name>
  equalled software-breakpoint - but that does not work (it did not send a Z0, but
  sent an X packet instead (verified with an earlier GDB compiled with tracing on)):

--------------------------------------------------------------------------------
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
0x0013c888 in ?? ()
(gdb) c
Continuing.
Warning:
Cannot insert breakpoint -1.
Error accessing memory address 0x110000: Input/output error.
--------------------------------------------------------------------------------

  I then also re-tried with <name> equal to binary-download - but that does not work
  (it did not send the X, but sent an M packet instead):

--------------------------------------------------------------------------------
(gdb) c
Continuing.
^C
Program received signal SIGTRAP, Trace/breakpoint trap.
Cannot remove breakpoints because program is no longer writable.
Further execution is probably impossible.
0x0013c880 in ?? ()
(gdb) 
--------------------------------------------------------------------------------

  Please could someone kindly shed light on this GDB behaviour?

  Thank you.

Anmol.


             reply	other threads:[~2009-07-24 21:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-24 21:12 Anmol P. Paralkar [this message]
2009-07-24 21:19 ` Daniel Jacobowitz
2009-07-24 22:01   ` Anmol P. Paralkar
2009-07-25  2:25     ` Daniel Jacobowitz
2009-07-27 17:35       ` Anmol P. Paralkar
2009-07-27 17:55         ` Michael Snyder

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=Pine.LNX.4.64.0907241042280.31686@lds03-tx32 \
    --to=anmol@freescale.com \
    --cc=gdb@sourceware.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