public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "mark at klomp dot org" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4313] New: fcore on 'sleep' process doesn't work on x86_64
Date: Tue, 03 Apr 2007 13:45:00 -0000 [thread overview]
Message-ID: <20070403144528.4313.mark@klomp.org> (raw)
As reported at https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=234879
The following fcore example doesn't work on x86_64:
sleep 1h & pid=$! ;sleep 1;fcore -o /tmp/sleep.core $pid
fcore (from CVS) takes a very long time (about 7 minutes) on the above example
and then generates the following stacktrace:
Exception in thread "main" inua.eio.BufferUnderflowException
at inua.eio.ByteBuffer.get(fcore)
at frysk.util.CoredumpAction$CoreMapsBuilder.buildMap(fcore)
at frysk.sys.proc.MapsBuilder.construct(fcore)
at frysk.sys.proc.MapsBuilder.construct(fcore)
at frysk.util.CoredumpAction.write_elf_file(fcore)
at frysk.util.CoredumpAction.allExistingTasksCompleted(fcore)
at frysk.proc.ProcBlockAction.checkFinish(fcore)
at frysk.proc.ProcBlockAction$ProcBlockTaskObserver$1.execute(fcore)
at frysk.event.EventLoop.runEventLoop(fcore)
at frysk.event.EventLoop.run(fcore)
at fcore.main(fcore)
Comment #3 From Phil Muldoon (pmuldoon@redhat.com) on 2007-04-03 08:56 EST
[reply] Private
Hi Mark,
Locally (from CVS) I cannot reproduce as I get:
[pmuldoon@localhost filesystems]$ sleep 1h & pid=$! ;sleep 1;fcore -o
/tmp/sleep.core $pid
[1] 8533
[pmuldoon@localhost filesystems]$
[pmuldoon@localhost filesystems]$ eu-readelf -h /tmp/sleep.core.8533
ELF Header:
Magic: 7f 45 4c 46 01 01 01 00 00 00 00 00 00 00 00 00
Class: ELF32
Data: 2's complement, little endian
Ident Version: 1 (current)
OS/ABI: UNIX - System V
ABI Version: 0
Type: CORE (Core file)
Additionally it completes in < 30 seconds. Is there access to your machine so I
can test?
Comment #4 From Mark Wielaard (mwielaard@redhat.com) on 2007-04-03 09:11 EST
[reply] Private
(In reply to comment #3)
> Locally (from CVS) I cannot reproduce as I get:
> [...]
> [pmuldoon@localhost filesystems]$ eu-readelf -h /tmp/sleep.core.8533
> > [...]
> Additionally it completes in < 30 seconds. Is there access to your machine so I
> can test?
Cool! That looks promising. I am using a x86_64 machine for my tests (looks you
use something 32 bits based). I'll try to find you on irc.gimp.org in #frysk to
coordinate a debugging session.
Thanks,
Mark
--
Summary: fcore on 'sleep' process doesn't work on x86_64
Product: frysk
Version: unspecified
Status: NEW
Severity: normal
Priority: P2
Component: general
AssignedTo: frysk-bugzilla at sourceware dot org
ReportedBy: mark at klomp dot org
http://sourceware.org/bugzilla/show_bug.cgi?id=4313
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-04-03 13:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-03 13:45 mark at klomp dot org [this message]
2007-04-03 14:05 ` [Bug general/4313] " pmuldoon at redhat dot com
2007-04-03 14:06 ` pmuldoon at redhat dot com
2007-04-03 14:24 ` mark at klomp dot org
2007-04-03 15:28 ` pmuldoon at redhat dot com
2007-04-04 15:06 ` mark at klomp dot org
2007-07-23 9:48 ` mark at klomp dot org
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=20070403144528.4313.mark@klomp.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=frysk-bugzilla@sourceware.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).