public inbox for gdb-prs@sourceware.org help / color / mirror / Atom feed
From: "tomas.vanek at fbl dot cz" <sourceware-bugzilla@sourceware.org> To: gdb-prs@sourceware.org Subject: [Bug breakpoints/28683] advance/until commands do not handle SIGTRAMP_FRAME on ARM Cortex-M Date: Fri, 10 Dec 2021 20:51:13 +0000 [thread overview] Message-ID: <bug-28683-4717-LO5Q6ENDTb@http.sourceware.org/bugzilla/> (raw) In-Reply-To: <bug-28683-4717@http.sourceware.org/bugzilla/> https://sourceware.org/bugzilla/show_bug.cgi?id=28683 tomas.vanek at fbl dot cz changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tomas.vanek at fbl dot cz --- Comment #1 from tomas.vanek at fbl dot cz --- At first I thought that the solution proposed for https://sourceware.org/bugzilla/show_bug.cgi?id=28549 would help here as well. But no luck, even if LR 0xffffffff is recognised as SIGTRAMP, 'advance'/'until' does not care of it. -- You are receiving this mail because: You are on the CC list for the bug.
next prev parent reply other threads:[~2021-12-10 20:51 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-12-10 20:28 [Bug breakpoints/28683] New: " tomas.vanek at fbl dot cz 2021-12-10 20:51 ` tomas.vanek at fbl dot cz [this message] 2021-12-14 17:27 ` [Bug breakpoints/28683] " tomas.vanek at fbl dot cz 2022-10-13 9:21 ` luis.machado at arm dot com 2022-10-14 11:26 ` tomas.vanek at fbl dot cz 2022-10-14 15:02 ` tomas.vanek at fbl dot cz 2022-10-16 15:28 ` tomas.vanek at fbl dot cz 2022-10-17 7:14 ` luis.machado at arm dot com 2022-10-21 10:02 ` luis.machado at arm dot com 2023-01-10 22:30 ` tomas.vanek at fbl dot cz 2023-01-10 22:32 ` tomas.vanek at fbl dot cz 2023-01-10 22:37 ` tomas.vanek at fbl dot cz
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-28683-4717-LO5Q6ENDTb@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).