mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Hui Zhu <teawater@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: [PATCH] Fix the multithread program core thread message error
Date: Tue, 30 Jun 2009 17:12:31 +0800	[thread overview]
Message-ID: <daef60380906300212p2a461537p9730686084a9ef8d@mail.gmail.com> (raw)

Fix the multithread program core thread message error.
The thread message of core file is generated in
elf_dump_thread_status.  The register values is set by
elf_core_copy_task_regs in this function.
static inline int elf_core_copy_task_regs(struct task_struct *t,
					   elf_gregset_t* elfregs)
{

	return ELF_CORE_COPY_TASK_REGS(t, elfregs);
	return 0;
}
If a arch doesn't define ELF_CORE_COPY_TASK_REGS, This function will do
nothing.  Then the core file will not have the register message of
thread.
So add elf_core_copy_regs to set regiser values if
ELF_CORE_COPY_TASK_REGS doesn't define.
---
 elfcore.h |    2 ++
 1 file changed, 2 insertions(+)

diff --git a/include/linux/elfcore.h b/include/linux/elfcore.h
index 7605c5e..03ec167 100644
--- a/include/linux/elfcore.h
+++ b/include/linux/elfcore.h
@@ -125,6 +125,8 @@ static inline int elf_core_copy_task_regs(struct
task_struct *t, elf_gregset_t*
 #ifdef ELF_CORE_COPY_TASK_REGS

        return ELF_CORE_COPY_TASK_REGS(t, elfregs);
+#else
+       elf_core_copy_regs(elfregs, task_pt_regs(t));
 #endif
        return 0;
 }

             reply	other threads:[~2009-06-30  9:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-30  9:12 Hui Zhu [this message]
2009-07-01  0:54 ` Amerigo Wang
2009-07-01  3:27   ` Hui Zhu
2009-07-01  3:29     ` Hui Zhu
2009-07-01  4:51     ` Amerigo Wang
2009-07-01  6:21       ` Hui Zhu
2009-07-01  7:20         ` Amerigo Wang
2009-07-01  8:16           ` Hui Zhu
2009-07-01 19:05         ` Andrew Morton
2009-07-01 19:19           ` Bill Gatliff
2009-07-03  9:48           ` Amerigo Wang

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=daef60380906300212p2a461537p9730686084a9ef8d@mail.gmail.com \
    --to=teawater@gmail.com \
    --cc=linux-kernel@vger.kernel.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®