mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: John Weber <weber@nyc.rr.com>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.5.4 Compile Error
Date: Mon, 11 Feb 2002 01:02:19 -0500	[thread overview]
Message-ID: <3C675E6B.4010605@nyc.rr.com> (raw)
In-Reply-To: <3C674CFA.2030107@nyc.rr.com> <3C6750CD.46575DAA@mandrakesoft.com>

Jeff Garzik wrote:
> John Weber wrote:
> 
>>/usr/src/linux-2.5.4/include/asm/processor.h: In function `thread_saved_pc':
>>/usr/src/linux-2.5.4/include/asm/processor.h:444: dereferencing pointer
>>to incomplete type
>>make: *** [init/main.o] Error 1
>>
> 
> since it's just for /usr/bin/ps, ie. not a fast path, I just un-inlined
> it in my alpha hacking.  Same approach might work for here, too.
> 
> The basic problem, I'm guessing, is that asm/processor.h wants to know
> about the internals of task struct, but it can't yet.
> 
> 	Jeff
> 

I don't know what the problem is, but un-inlining this function isn't 
correcting it.

The function thread_saved_pc() is a mystery to me.  It is declared with 
a return type of unsigned long, and yet return this:

((unsigned long *)tsk->thread->esp)[3]

This is confusing to me in many ways:
- the "thread" member of task struct is not a pointer
- esp is of type unsigned long, so I don't understand the cast, and
I certainly don't understand the [3] here.

Can anyone explain this code to me?

I'm a kernelnewbie, so I'm inclined to return:
return (tsk->thread).esp
What is this function trying to do?


  reply	other threads:[~2002-02-11  6:02 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-11  4:47 John Weber
2002-02-11  5:04 ` Jeff Garzik
2002-02-11  6:02   ` John Weber [this message]
2002-02-11  6:29     ` Andrew Morton
2002-02-11  6:33     ` David S. Miller
2002-02-11  6:48       ` Andrew Morton
2002-02-11  6:52       ` David S. Miller
2002-02-11  6:20   ` Robert Love
2002-02-11  6:36     ` John Weber
2002-02-11  6:50     ` Robert Love
2002-02-11 15:50     ` Pascal Schmidt

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=3C675E6B.4010605@nyc.rr.com \
    --to=weber@nyc.rr.com \
    --cc=jgarzik@mandrakesoft.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®