All of lore.kernel.org
 help / color / mirror / Atom feed
From: cminyard@mvista.com (Corey Minyard)
To: linux-arm-kernel@lists.infradead.org
Subject: kgdb on ARM printing a bogus OOPs
Date: Thu, 17 Apr 2014 12:15:11 -0500	[thread overview]
Message-ID: <53500C1F.3040505@mvista.com> (raw)

I was playing with kgdb on ARM, and I noticed that every time it hits a
breakpoint I get the following:

  Internal error: Oops - undefined instruction: 0 [#3] PREEMPT SMP ARM

It's mostly harmless, the breakpoints still work, but all the printks
could be troublesome in some debugging situations.  It's there because
the notify_die() call was added after the printk in question.  I'd guess
it should be before the printk, but is there a reason it was added after?

Thanks,

-corey

                 reply	other threads:[~2014-04-17 17:15 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=53500C1F.3040505@mvista.com \
    --to=cminyard@mvista.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.