public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "michaelwoerister at posteo dot net" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug tdep/17521] New: On Windows-x86_64 GDB runs into infinite loop when entering small functions generated by RUSTC/LLVM Date: Wed, 29 Oct 2014 15:16:00 -0000 [thread overview] Message-ID: <bug-17521-4717@http.sourceware.org/bugzilla/> (raw) https://sourceware.org/bugzilla/show_bug.cgi?id=17521 Bug ID: 17521 Summary: On Windows-x86_64 GDB runs into infinite loop when entering small functions generated by RUSTC/LLVM Product: gdb Version: 7.8 Status: NEW Severity: normal Priority: P2 Component: tdep Assignee: unassigned at sourceware dot org Reporter: michaelwoerister at posteo dot net Created attachment 7861 --> https://sourceware.org/bugzilla/attachment.cgi?id=7861&action=edit Source+Executable for reproducing - use 'rb tiny_func' to set breakpoint and then 'run' Using the GDB version coming with [1], GDB seems to get stuck when entering some small functions generated by the Rust compiler. Sample backtraces [2] seem to suggest that control flow never leaves the `amd64_windows_frame_decode_insns()` function. Attached you can find a small program for reproducing the bug. Just set a breakpoint with `rb tiny_func` and then `run`. Feel free to contact me if you have any further questions. [1] http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.1/threads-win32/seh/x86_64-4.9.1-release-win32-seh-rt_v3-rev2.7z/download [2] https://github.com/rust-lang/rust/issues/17540#issuecomment-60264838 -- You are receiving this mail because: You are on the CC list for the bug.
next reply other threads:[~2014-10-29 15:16 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-10-29 15:16 michaelwoerister at posteo dot net [this message] 2014-11-10 14:28 ` [Bug tdep/17521] " cvs-commit at gcc dot gnu.org 2014-11-12 4:52 ` cvs-commit at gcc dot gnu.org 2014-11-17 17:06 ` cvs-commit at gcc dot gnu.org 2020-04-01 18:11 ` tromey at sourceware 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=bug-17521-4717@http.sourceware.org/bugzilla/ \ --to=sourceware-bugzilla@sourceware.org \ --cc=gdb-prs@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).