mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jason Wessel <jason.wessel@windriver.com>
To: torvalds@linux-foundation.org
Cc: linux-kernel@vger.kernel.org, kgdb-bugreport@lists.sourceforge.net
Subject: [git pull] kgdb 2.6.27 fixes
Date: Fri,  1 Aug 2008 10:27:51 -0500	[thread overview]
Message-ID: <1217604474-24239-1-git-send-email-jason.wessel@windriver.com> (raw)


Linus, please pull the kgdb git tree fixes for 2.6.27.

  git://git.kernel.org/pub/scm/linux/kernel/git/jwessel/linux-2.6-kgdb.git for_linus


Summary: 

Several regressions have been fixed for which there was no automated test.
 - There is no requirement for CONFIG_FRAME_POINTER.
 - When using CONFIG_DEBUG_RODATA kgdb silently failed to set
   breakpoints instead of reporting an error.
 - The ability to query for the thread list from the debugger
   would silently hang the kernel.

---

Jason Wessel (3):
      kgdb: remove the requirement for CONFIG_FRAME_POINTER
      kgdb: fix kgdb_validate_break_address to perform a mem write
      kgdb: fix gdb serial thread queries

 Documentation/DocBook/kgdb.tmpl |   18 +++++++
 kernel/kgdb.c                   |   94 ++++++++++++++++++++++++++++----------
 lib/Kconfig.kgdb                |   11 +++--
 nus, please pull kgdb the kgdb git tree.
3 files changed, 94 insertions(+), 29 deletions(-)

             reply	other threads:[~2008-08-01 15:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-01 15:27 Jason Wessel [this message]
2008-08-01 15:27 ` [PATCH 1/3] kgdb: remove the requirement for CONFIG_FRAME_POINTER Jason Wessel
2008-08-01 15:27   ` [PATCH 2/3] kgdb: fix kgdb_validate_break_address to perform a mem write Jason Wessel
2008-08-01 15:27     ` [PATCH 3/3] kgdb: fix gdb serial thread queries Jason Wessel

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=1217604474-24239-1-git-send-email-jason.wessel@windriver.com \
    --to=jason.wessel@windriver.com \
    --cc=kgdb-bugreport@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®