public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "pmuldoon at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/5383] New: fhpd peek with no parameters spawns an NPE Date: Wed, 21 Nov 2007 10:00:00 -0000 [thread overview] Message-ID: <20071121100017.5383.pmuldoon@redhat.com> (raw) [pmuldoon@localhost frysk_bin]$ ./frysk-core/frysk/bindir/fhpd core.25927 /bin/sleep Attached to core file: /home/pmuldoon/frysk_bin/core.25927 (fhpd) where [0.0] #0 0x00000038cba9ac30 in __nanosleep_nocancel () from /lib64/libc.so.6 #1 0x0000000000402f1b in [unknown] from /bin/sleep #2 0x0000000000402a44 in [unknown] from /bin/sleep #3 0x000000000040158c in [unknown] from /bin/sleep #4 0x00000038cba1e074 in __libc_start_main () from /lib64/libc.so.6 #5 0x00000000004011d9 in [unknown] from /bin/sleep (fhpd) peek [0.0] Internal Error: java.lang.NullPointerException at frysk.hpd.Input.parameter(fhpd) at frysk.hpd.PeekCommand.interpret(fhpd) at frysk.hpd.ParameterizedCommand.interpret(fhpd) at frysk.hpd.MultiLevelCommand.interpret(fhpd) at frysk.hpd.CLI.execCommand(fhpd) at frysk.bindir.fhpd.main(fhpd) -- Summary: fhpd peek with no parameters spawns an NPE Product: frysk Version: unspecified Status: NEW Severity: normal Priority: P2 Component: general AssignedTo: frysk-bugzilla at sourceware dot org ReportedBy: pmuldoon at redhat dot com CC: rmoseley at redhat dot com http://sourceware.org/bugzilla/show_bug.cgi?id=5383 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next reply other threads:[~2007-11-21 10:00 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-11-21 10:00 pmuldoon at redhat dot com [this message] 2007-11-21 10:03 ` [Bug general/5383] " pmuldoon at redhat dot com
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=20071121100017.5383.pmuldoon@redhat.com \ --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: linkBe 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).