From: Carlos O'Donell <carlos@baldric.uwo.ca>
To: "Boehm, Hans" <hans_boehm@hp.com>
Cc: "'parisc-linux@lists.parisc-linux.org'"
<parisc-linux@lists.parisc-linux.org>
Subject: Re: [parisc-linux] Program counter from sigcontext, constructurs and -fPIC
Date: Fri, 25 Apr 2003 16:52:59 -0400 [thread overview]
Message-ID: <20030425205259.GG32717@systemhalted> (raw)
In-Reply-To: <75A9FEBA25015040A761C1F74975667D01442051@hplex4.hpl.hp.com>
Hans,
> It's a new, currently rather simple, but thread-compatible, purely user-level, profiler. It includes some infrastructure for using hardware atomic operations in reasonably portable ways. Need less to say, PA-RISC makes a wonderful test case.
Cool. (Could you please make your MUA wrap lines at a reasonable length?).
> > A. What kernel are you using?
> 2.4.17-64 on spe170.testdrive.hp.com.
Needs updating :)
> Once you get the PC in the signal handler, that's easy. It sounds like getting the PC from a signal handler from a 32-bit executable on a 64-bit kernel is currently impossible? I should probably focus on 64-bit executables? Or does profil() have a way to get around the problem?
64-bit executables don't exist in Linux .... I'm working on it, if you
want to get into the glibc port please talk to me off-list :)
64-bit kernels spill 64-bit values into the 32-bit values of the
sigcontext struct. Which means you get everything in the wrong place and
much larger than you expected. This _has_ to be fixed soon, perhaps I'll
look at this code next.
c.
next prev parent reply other threads:[~2003-04-25 20:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-25 19:40 [parisc-linux] Program counter from sigcontext, constructurs and -fPIC Boehm, Hans
2003-04-25 19:56 ` [parisc-linux] Program counter from sigcontext, constructurs John David Anglin
2003-04-25 20:52 ` Carlos O'Donell [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-04-30 0:52 [parisc-linux] Program counter from sigcontext, constructurs and -fPIC Boehm, Hans
2003-04-29 21:17 Boehm, Hans
2003-04-29 21:30 ` Carlos O'Donell
2003-04-29 22:13 ` Grant Grundler
2003-04-30 0:31 ` Carlos O'Donell
2003-04-30 5:18 ` Grant Grundler
2003-04-30 7:15 ` Joel Soete
2003-04-30 18:12 ` Carlos O'Donell
2003-05-03 20:48 ` Joel Soete
2003-05-05 6:08 ` Joel Soete
2003-05-01 4:09 ` Grant Grundler
2003-04-25 17:46 Boehm, Hans
2003-04-25 18:54 ` Carlos O'Donell
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=20030425205259.GG32717@systemhalted \
--to=carlos@baldric.uwo.ca \
--cc=hans_boehm@hp.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.