public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "jan dot kratochvil at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/3917] libunwind: Nested functions resolving broken Date: Wed, 24 Jan 2007 18:20:00 -0000 [thread overview] Message-ID: <20070124182034.7490.qmail@sourceware.org> (raw) In-Reply-To: <20070124181836.3917.jan.kratochvil@redhat.com> ------- Additional Comments From jan dot kratochvil at redhat dot com 2007-01-24 18:20 ------- [mistaken commit] Bug 3791 frysk-unwinder-update.patch http://sourceware.org/bugzilla/attachment.cgi?id=1491&action=view sometimes could fail on: fstack: ../../frysk/frysk-imports/lib/unwind/cni/FrameCursor.cxx:86: void lib::unwind::FrameCursor::create_frame_cursor(jlong): Assertion `ip == offset + proc_info.start_ip' failed. That is correct as part of libunwind apparently supports nested functions but the other part not: ip=0xb2ee46,offset=0xc,proc_info.start_ip=0xb2ee30,buf="__pause_nocancel" 969: 00b2ee30 101 FUNC WEAK DEFAULT 11 pause@@GLIBC_2.0 4235: 00b2ee3a 20 FUNC LOCAL DEFAULT 11 __pause_nocancel Currect: offset=0xc,proc_info.start_ip=0xb2ee3a,buf="__pause_nocancel" -- What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |ASSIGNED http://sourceware.org/bugzilla/show_bug.cgi?id=3917 ------- 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-01-24 18:20 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-01-24 18:18 [Bug general/3917] New: " jan dot kratochvil at redhat dot com 2007-01-24 18:20 ` jan dot kratochvil at redhat dot com [this message] 2007-01-25 19:00 ` [Bug general/3917] " jan dot kratochvil 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=20070124182034.7490.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).