All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] KGDB set / remove breakpoints
Date: Tue, 20 Apr 2010 02:15:01 -0400	[thread overview]
Message-ID: <201004200215.02118.vapier@gentoo.org> (raw)
In-Reply-To: <m2u73f9cf91004190154q6c14fda8rea90ec1b2f780aee@mail.gmail.com>

On Monday 19 April 2010 04:54:50 Tonny Tzeng wrote:
> >> Please note, after applying this patch, those architectures, which
> >> already enabled KGDB support, have to create a new asm/kgdb.h and
> >> define the length of the break instruction (BREAK_INSTR_SIZE) in that
> >> file.
> > 
> > i dont think breaking build is a good idea.  i would have the code simply
> > disable itself if BREAK_INSTR_SIZE isnt set.
> 
> That's why I used ifndef in the previous patch, and set
> BREAK_INSTR_SIZE to 4 if it isn't set, but I thought you prefer "an
> undefined size should be used as a tip that the arch doesnt yet
> support break points"?

i meant have the functions always return an error.  have the header do:
#ifndef BREAK_INSTR_SIZE
#define BREAK_INSTR_SIZE 0
#endif

and then in gdb_cmd_break(), do something at the top like:
if (BREAK_INSTR_SIZE == 0)
	return;

> In Linux kgdb code, there is an arch independent header file
> include/linux/kgdb.h, which includes arch dependent header asm/kgdb.h.
>  I am trying to include this concept here, unfortunately current
> u-boot code only has linux/kgdb.h, if we want to define arch specific
> code in asm/kgdb.h, we may need to include asm/kgdb.h from
> linux/kgdb.h, so it looks to me it will definitely break other arch,
> do you have any suggestion for that?

just post a patch to add asm/kgdb.h stubs for the few arches that you dont 
implement yourself.  i think only blackfin/i386/ppc support kgdb atm.
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20100420/e316eefb/attachment.pgp 

  reply	other threads:[~2010-04-20  6:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-17 17:20 [U-Boot] [PATCH] KGDB set / remove breakpoints Tonny Tzeng
2010-04-17 17:46 ` Mike Frysinger
2010-04-19  8:54   ` Tonny Tzeng
2010-04-20  6:15     ` Mike Frysinger [this message]
2010-04-17 18:10 ` [U-Boot] [PATCH v2 0/4] [ARM] Add KGDB support for ARM platforms Tonny Tzeng
2010-04-17 18:12   ` [U-Boot] [PATCH v2 1/4] " Tonny Tzeng
2010-04-17 18:15     ` [U-Boot] [PATCH v2 2/4] " Tonny Tzeng
2010-04-17 18:16       ` [U-Boot] [PATCH v2 3/4] " Tonny Tzeng
2010-04-17 18:18       ` [U-Boot] [PATCH v2 4/4] " Tonny Tzeng
2010-04-20  6:17   ` [U-Boot] [PATCH v2 0/4] " Mike Frysinger

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=201004200215.02118.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.