From: mgross <mgross@unix-os.sc.intel.com>
To: vamsi_krishna@in.ibm.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Multi-threaded core dumps for 2.5.21.
Date: Tue, 18 Jun 2002 09:03:14 -0400 [thread overview]
Message-ID: <200206181555.g5IFtuP32608@unix-os.sc.intel.com> (raw)
In-Reply-To: <200206181332.g5IDW5r54694@westrelay01.boulder.ibm.com>
On Tuesday 18 June 2002 09:41 am, Vamsi Krishna S. wrote:
> Mark,
>
> You are capturing the registers of the thread dumping core
> twice in this patch. Please apply on top of your patch:
You are so right! That same code is defined as an inline in elfcore.h, and
is executed just a few lines down from there. I'll incorporate this into a
couple of new patches for a posting later today.
Thanks for the review.
--mgross
>
> --- tcore/fs/binfmt_elf.c.ori Mon Jun 17 15:02:27 2002
> +++ tcore/fs/binfmt_elf.c Mon Jun 17 15:02:49 2002
> @@ -1203,22 +1203,6 @@
>
> }
>
> - memset(&prstatus, 0, sizeof(prstatus));
> - /*
> - * This transfers the registers from regs into the standard
> - * coredump arrangement, whatever that is.
> - */
> -#ifdef ELF_CORE_COPY_REGS
> - ELF_CORE_COPY_REGS(prstatus.pr_reg, regs)
> -#else
> - if (sizeof(elf_gregset_t) != sizeof(struct pt_regs))
> - {
> - printk("sizeof(elf_gregset_t) (%ld) != sizeof(struct pt_regs) (%ld)\n",
> - (long)sizeof(elf_gregset_t), (long)sizeof(struct pt_regs));
> - }
> - else
> - *(struct pt_regs *)&prstatus.pr_reg = *regs;
> -#endif
>
> /* capture the status of all other threads */
> if (signr) {
>
>
> Same problem is there on the patch you posted for 2.4.18 too, the above
> will apply with a slight offset.
>
> Vamsi Krishna S.
> Linux Technology Center,
> IBM Software Lab, Bangalore.
> Ph: +91 80 5044959
> Internet: vamsi_krishna@in.ibm.com
>
> On Sat, 15 Jun 2002 04:45:56 +0530, mgross wrote:
> > Attached is a re-base of the 2.5.18 patch posted last week.
> >
> > This patch has been tested on my SMP system and seems very stable, so
> > far. I would like very much to see this feature added to the 2.5.x
> > kernels and more milage given to it.
> >
> > For ISV's not having the ability to create core dumps for pthread
> > applications is a strong justification for not using Linux. Now is a good
> > time for Linux support the ISV's WRT core files for multi-threaded
> > applications.
> >
> > To use the core files from multi-threaded applications, created with this
> > patch you may need to strip the objects from /lib/libpthread. For my
> > system 'strip /lib/libpthread-0.9.so makes things good, YMMV.
> >
> > Please apply this patch.
> >
> > --mgross
next prev parent reply other threads:[~2002-06-18 15:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 20:17 mgross
2002-06-18 13:41 ` Vamsi Krishna S.
2002-06-18 13:03 ` mgross [this message]
2002-06-18 19:27 ` mgross
2002-06-18 19:47 ` [PATCH] TCore patch for 2.5.22 mgross
2002-06-18 20:40 ` mgross
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=200206181555.g5IFtuP32608@unix-os.sc.intel.com \
--to=mgross@unix-os.sc.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vamsi_krishna@in.ibm.com \
/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®