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/4777] fd smash from Elf exception Date: Thu, 12 Jul 2007 14:17:00 -0000 [thread overview] Message-ID: <20070712141704.13011.qmail@sourceware.org> (raw) In-Reply-To: <20070711170852.4777.cagney@redhat.com> ------- Additional Comments From pmuldoon at redhat dot com 2007-07-12 14:17 ------- The problem is in part the way the Elf object is being used in various parts of Frysk's code like this: try { elf = new Elf(proc.getExe(), ElfCommand.ELF_C_READ); dwarf = new Dwarf(elf, DwarfCommand.READ, null); } catch (lib.elf.ElfException ignore) { // FIXME: Why is this ignored? } The problem here is two-fold. The elf exception should be caught in it's own try, not in a composite try block and dealt with. And the code should fail at that point. Also fd = 0 was a poor choice of an initial value in the Elf's native code. The other part if that that Elf object is not valid, yet still allows access to the native sections. In Java, a constructor is never allowed to return null, so I suggest we gate further calls with a boolean gate. something like nativeSuccess = true. -- http://sourceware.org/bugzilla/show_bug.cgi?id=4777 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-07-12 14:17 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-07-11 17:09 [Bug general/4777] New: " cagney at redhat dot com 2007-07-12 14:17 ` pmuldoon at redhat dot com [this message] 2007-07-12 22:45 ` [Bug general/4777] " cagney 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=20070712141704.13011.qmail@sourceware.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: 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).