public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "bohdan200 at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug breakpoints/27509] ARM Cortex-M7: Setting breakpoint and stepping through causes internal error at function 'finish_step_over'
Date: Thu, 16 Mar 2023 07:59:56 +0000	[thread overview]
Message-ID: <bug-27509-4717-Ogo8brROKl@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27509-4717@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=27509

Bohdan Tymkiv <bohdan200 at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bohdan200 at gmail dot com

--- Comment #3 from Bohdan Tymkiv <bohdan200 at gmail dot com> ---
Hello gentlemen,

>> JLinkGDBServer: JLinkARM.dll V6.90a (DLL compiled Dec 14 2020 17:13:26)
>> Launch JLinkGDBServer with the flag `-rtos GDBServer/RTOSPlugin_ChibiOS`

This is not an OpenOCD, OP is definitely using native SEGGER tools.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2023-03-16  7:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-04  1:15 [Bug breakpoints/27509] New: " egarcia.charger at gmail dot com
2021-03-04  1:16 ` [Bug breakpoints/27509] " egarcia.charger at gmail dot com
2021-03-04 15:50 ` simark at simark dot ca
2022-11-29 20:39 ` tromey at sourceware dot org
2023-03-16  7:59 ` bohdan200 at gmail dot com [this message]
2023-03-29 12:14 ` luis.machado at arm 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=bug-27509-4717-Ogo8brROKl@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: link
Be 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).