public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jiang <djiang@mvista.com>
To: Petr Vandrovec <vandrove@vc.cvut.cz>
Cc: Andi Kleen <ak@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: x86_64 frame pointer via thread context
Date: Mon, 08 Aug 2005 14:09:13 -0700	[thread overview]
Message-ID: <42F7C9F9.7000505@mvista.com> (raw)
In-Reply-To: <42F7C01E.4020108@vc.cvut.cz>

Petr Vandrovec wrote:
>>> Replace call to sleep() with busy loop.  Glibc's sleep() uses %ebp for
>>> its own data, so when you interrupt sleep(), you get rbp=(unsigned 
>>> int)-1,
>>> as rbp really contains 0x0000.0000.ffff.ffff when nanosleep() syscall
>>> is issued.
>>>                                 Petr
>>  From what I understand, when you signal a thread, the signal handler 
>> executes in the thread context and not the main process context. So 
>> therefore the rbp would be the thread's copy and not the one that 
>> sleep() just modified. So whatever sleep does to the main process 
>> context, there shouldn't be any effect on the thread context.... Also, 
>> what can I call to allow the threads to run? sleep() allows me to run 
>> the other threads. Busy wait does not.....
> 
> 
> I do not understand.  You call sleep() from both threads you spawn
> (as well from main), so both threads are always interrupted in the
> sleep(2).  Load your process to the debugger...
> 
> #0  tb_sig_handler (sig=33, info=0x407ff2f0, ucontext=0x407ff1c0) at 
> ttest1.c:26
> #1  <signal handler called>
> #2  0x00002aaaaad81335 in nanosleep () from /lib/libc.so.6
> #3  0x00002aaaaad811a5 in sleep () from /lib/libc.so.6
> #4  0x0000000000400871 in test_thread1 (arg=0x0) at ttest1.c:40
> #5  0x00002aaaaabc6b55 in start_thread () from /lib/libpthread.so.0
> #6  0x00002aaaaada87f0 in clone () from /lib/libc.so.6

Ooops, you are right. I forgot about those ones in the threads. Yes you 
are right. Once the sleep goes away rBP displays the correct values. Is 
this issue due to glibc or because of the toolchain? I do not have this 
issues on 32bit x86.... I would assume that the reason it works on 
Mandrake is due to the toolchain they use versus other distros? The 
toolchain determines which registers to use and the 
-fno-omit-frame-pointer did not prevent some of them from clobbering rbp?

-- 
Dave

------------------------------------------------------
Dave Jiang
Software Engineer          Phone: (480) 517-0372
MontaVista Software, Inc.    Fax: (480) 517-0262
2141 E Broadway Rd, St 108   Web: www.mvista.com
Tempe, AZ  85282          mailto:djiang@mvista.com
------------------------------------------------------


  reply	other threads:[~2005-08-08 21:09 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <42F3EC97.2060906@mvista.com.suse.lists.linux.kernel>
2005-08-06 11:54 ` x86_64 frame pointer via thread context Andi Kleen
2005-08-08  7:13   ` Jan Engelhardt
2005-08-08 17:27     ` Dave Jiang
2005-08-08 17:35       ` Dave Jiang
2005-08-08 18:35   ` Dave Jiang
2005-08-08 20:06     ` Petr Vandrovec
2005-08-08 20:19       ` Dave Jiang
2005-08-08 20:27         ` Petr Vandrovec
2005-08-08 21:09           ` Dave Jiang [this message]
2005-08-08 22:29             ` Petr Vandrovec
2005-08-05 22:47 Dave Jiang

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=42F7C9F9.7000505@mvista.com \
    --to=djiang@mvista.com \
    --cc=ak@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vandrove@vc.cvut.cz \
    /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