public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: <duane@duaneellis.com>
To: "taylor,  david" <david.taylor@emc.com>,
	 "gdb@sourceware.org" <gdb@sourceware.org>
Subject: RE: (hardware) watchpoints and actions
Date: Thu, 12 Nov 2015 22:34:00 -0000	[thread overview]
Message-ID: <20151112153355.5c1bb9f86d671edec44bb378f25c04cc.075c0da967.wbe@email03.secureserver.net> (raw)

duane> a) Most "gdb-server" type things are rather "dumb" they do not
know what symbols are.

david> [snip; see] maint agent [snip]

david> Our stubs (both old and new) contain substantial tracepoint
support. 

Hmm, you learn something every day. 

I am very familiar with several gdbserver JTAG type debug environments
(mostly bare metal), where this feature is *NOT* supported. I have spent
very little time in the linux based gdb-server, hence my ignorance of
this feature.

david> The code *IS* compiled into the application. The GDB stub is
always compiled in. 

Yes, that is quite a different environment then my background. 

Paul @ Dell - brings up another point - security/access control to the
GDB stub feature. 

In your case "compiled-in-gdb-stub" is a product requirement, and/or
product feature. 

In the space constrained world (ie: micro controller, and/or bare-metal)

(1) you often don't have code/ram space for items like this, 
(2) for performance reasons, this code must be removed
(3) There is no support for this in the underling operating system (if
there is one)
(4) Or the GDB server exists external to the target (ie: JTAG)

Each of us come from different backgrounds.

-Duane.

             reply	other threads:[~2015-11-12 22:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-12 22:34 duane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2015-11-12 16:14 duane
2015-11-12 20:45 ` taylor, david
2015-11-12 20:50   ` Paul_Koning
2015-11-11 22:02 duane
2015-11-12 15:43 ` taylor, david
2015-11-11 18:01 taylor, david
2015-11-13 14:55 ` Yao Qi

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=20151112153355.5c1bb9f86d671edec44bb378f25c04cc.075c0da967.wbe@email03.secureserver.net \
    --to=duane@duaneellis.com \
    --cc=david.taylor@emc.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).