From: Phil Muldoon <pmuldoon@redhat.com>
To: Mark Wielaard <mark@klomp.org>
Cc: Frysk Hackers <frysk@sourceware.org>
Subject: Re: [stack] segment only corefiles, and [vdso]
Date: Tue, 26 Feb 2008 16:01:00 -0000 [thread overview]
Message-ID: <47C437B1.3000507@redhat.com> (raw)
In-Reply-To: <1204041406.3487.58.camel@dijkstra.wildebeest.org>
Mark Wielaard wrote:
> Hi Phil,
>
> On Tue, 2008-02-26 at 15:19 +0000, Phil Muldoon wrote:
>
>> When I implemented that experimental feature, I only included the
>> [stack] segment. However on IA32, there is always a visit to the [vdso]
>> segment which I did not include.
>>
>
> What is the visit from/for?
>
Well it appears to happen on every IA32 process. Why/to ... not terribly
sure other than every process/corefile seems to include a visit there.
just fstack a 32 bit process.
Regards
Phil
> Cheers,
>
> Mark
>
>
next prev parent reply other threads:[~2008-02-26 16:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-26 15:19 Phil Muldoon
2008-02-26 15:57 ` Mark Wielaard
2008-02-26 16:01 ` Phil Muldoon [this message]
2008-02-26 16:16 ` Mark Wielaard
2008-02-26 16:49 ` Phil Muldoon
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=47C437B1.3000507@redhat.com \
--to=pmuldoon@redhat.com \
--cc=frysk@sourceware.org \
--cc=mark@klomp.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).