All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Gross <mark@thegnar.org>
To: phil-list@redhat.com, Daniel Jacobowitz <dan@debian.org>,
	Mark Kettenis <kettenis@gnu.org>,
	mgross <mgross@unix-os.sc.intel.com>
Cc: linux-kernel@vger.kernel.org,
	NPT library mailing list <phil-list@redhat.com>
Subject: Re: [patch] thread-aware coredumps, 2.5.43-C3
Date: Fri, 18 Oct 2002 06:57:38 -0700	[thread overview]
Message-ID: <200210180657.38291.mark@thegnar.org> (raw)
In-Reply-To: <20021018004847.GA27817@nevyn.them.org>

I think I fixed it to set namesz to 5, with the +1 it was making it 6.  My 
patch is supposed to remove the +1.

The value for men-name for the extended registers case is "LINUX".

--mgross

On Thursday 17 October 2002 05:48 pm, Daniel Jacobowitz wrote:
> You'd have to ask Mark Kettenis about that.  Mark, it looks like you
> updated the kernel to write namesz == 6, but BFD still expects 5 (and
> elfcore_write_note writes 6)?  Shouldn't we accept both, anyway?
>
> On Thu, Oct 17, 2002 at 05:07:41PM -0400, mgross wrote:
> > This patch is working pretty well for me with only one problem, which
> > seems to have happened indepently of Ingo's patch.
> >
> > Extended floating point note sections are no longer getting recognized by
> > GDB 5.x.
> >
> > After a bit of poking around in the GDB 5.2.1 code (line 6399 bfd/efl.c)
> > I noticed that there is a n_namesz test for the reg-xfp section parsing.
> >
> > The following minor tweak on top of Ingo's patch  to binfmt_elf.c fixes
> > the problem.
> >
> > diff -urN -X dontdiff linux-2.5.43/fs/binfmt_elf.c
> > linux-2.5.43.xfp/fs/binfmt_elf.c
> > --- linux-2.5.43/fs/binfmt_elf.c      Thu Oct 17 16:54:13 2002
> > +++ linux-2.5.43.xfp/fs/binfmt_elf.c  Thu Oct 17 16:53:00 2002
> > @@ -964,7 +964,9 @@
> >  {
> >       struct elf_note en;
> >  
> > -     en.n_namesz = strlen(men->name) + 1;
> > +     en.n_namesz = strlen(men->name);
> > +     /* en.n_namesz = strlen(men->name) + 1;  gdb checks namez and the +
> > 1 */ +                                     /*breaks xfp core file note
> > sections. */ en.n_descsz = men->datasz;
> >       en.n_type = men->type;
> >  
> >
> >
> > I don't know when this +1 was added to writenote binfmt_elf.c or why.  I
> > do know that newer than July and it isn't in 2.4
> >
> > If there the + 1 is needed of others then we may need to special case the
> > NT_PRXFPREG note sections.
> >
> > --mgross


  reply	other threads:[~2002-10-18 13:53 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-08 12:09 [patch] thread-aware coredumps part 1, tcore-2.5.41-A6 Ingo Molnar
2002-10-08 13:30 ` mgross
2002-10-17  9:11   ` [patch] thread-aware coredumps, 2.5.43-C3 Ingo Molnar
2002-10-17 16:40     ` Daniel Jacobowitz
2002-10-21 14:29       ` Alan Cox
2002-10-21 14:54         ` Daniel Jacobowitz
2002-10-21 16:16           ` Alan Cox
2002-10-21 16:04             ` Daniel Jacobowitz
2002-10-17 21:07     ` mgross
2002-10-18  0:48       ` Daniel Jacobowitz
2002-10-18 13:57         ` Mark Gross [this message]
2002-10-18 14:03           ` Mark Gross
2002-10-19 13:26           ` Mark Kettenis
2002-10-19 19:26           ` Bill Davidsen
2002-10-19 19:34             ` Ulrich Drepper
2002-10-19 13:20         ` Mark Kettenis
2002-10-19 18:42           ` Mark Gross
2002-10-18  1:10     ` Andi Kleen
2002-10-18  1:35       ` Mark Gross
2002-10-18  2:12         ` Andi Kleen
2002-10-18  2:58           ` Mark Gross
2002-10-18  3:55             ` Daniel Jacobowitz
2002-10-18 14:00               ` mgross
2002-10-21 15:17             ` Pavel Machek
2002-11-03  7:32               ` Ulrich Drepper
2002-10-19 17:32     ` Ulrich Drepper
2002-10-18  2:23   ` Ulrich Drepper
2002-10-18  2:40     ` Andi Kleen
2002-10-08 18:04 ` [patch] thread-aware coredumps part 1, tcore-2.5.41-A6 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=200210180657.38291.mark@thegnar.org \
    --to=mark@thegnar.org \
    --cc=dan@debian.org \
    --cc=kettenis@gnu.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mgross@unix-os.sc.intel.com \
    --cc=phil-list@redhat.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 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.