All of lore.kernel.org
 help / color / mirror / Atom feed
From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: Jakub Jelinek <jakub@redhat.com>
Cc: libc-alpha <libc-alpha@sources.redhat.com>,
	parisc-linux@lists.parisc-linux.org
Subject: [parisc-linux] Re: [PATCH] _STACK_GROWS_UP fixes.
Date: Wed, 15 Oct 2003 12:40:47 -0400	[thread overview]
Message-ID: <20031015164047.GA31385__11911.8418232121$1416622878$gmane$org@systemhalted> (raw)
In-Reply-To: <20031015053431.GE12344@sunsite.ms.mff.cuni.cz>

On Wed, Oct 15, 2003 at 07:34:31AM +0200, Jakub Jelinek wrote:
> On Sun, Oct 12, 2003 at 05:37:34PM -0400, Carlos O'Donell wrote:
> > 2003-10-06  Carlos O'Donell <carlos@baldric.uwo.ca>
> > 
> > 	* pthread.c (__pthread_self_stack): _STACK_GROWS_UP case added.
> > 	(__pthread_find_self): Likewise.
> > 	* manager.c (thread_segment): _STACK_GROWS_UP case added.
> 
> You need to look at linuxthreads/attr.c (__pthread_attr_getstack) too
> (the recent code which parses /proc/self/maps and finds stack VMA in there).

That should hopefully explain the regression in tst-attr1, I hadn't
tracked it down yet, but I knew that some other STACK_GROWS_UP problems
might exist.

Thanks Jakub.

c.

  parent reply	other threads:[~2003-10-15 16:40 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-12 21:37 [parisc-linux] [PATCH] _STACK_GROWS_UP fixes Carlos O'Donell
2003-10-15  5:34 ` [parisc-linux] " Jakub Jelinek
2003-10-15  5:34 ` Jakub Jelinek
2003-10-15 16:40   ` Carlos O'Donell
2003-10-15 16:40   ` Carlos O'Donell [this message]
2003-10-18 22:55   ` Carlos O'Donell
2003-10-18 22:55   ` Carlos O'Donell
2003-10-15  5:53 ` Ulrich Drepper
2003-10-15  5:53 ` Ulrich Drepper

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='20031015164047.GA31385__11911.8418232121$1416622878$gmane$org@systemhalted' \
    --to=carlos@baldric.uwo.ca \
    --cc=jakub@redhat.com \
    --cc=libc-alpha@sources.redhat.com \
    --cc=parisc-linux@lists.parisc-linux.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.