All of lore.kernel.org
 help / color / mirror / Atom feed
From: "François Legal" <devel@thom.fr.eu.org>
To: "Jan Kiszka" <jan.kiszka@siemens.com>
Cc: xenomai@lists.linux.dev
Subject: Re: Watchpoints not being handled correctly on arm it seems
Date: Thu, 09 Nov 2023 15:38:38 +0100	[thread overview]
Message-ID: <10237-654cef00-d-68598f00@146937372> (raw)
In-Reply-To: <bf9d4965-6f5e-4862-a24e-9c1748bf9496@siemens.com>

Le Jeudi, Novembre 09, 2023 12:22 CET, Jan Kiszka <jan.kiszka@siemens.com> a écrit:

> On 08.11.23 17:58, François Legal wrote:
> > Hello,
> >
> > Working with xenomai 3.2.3 with linux 5.4 on Zynq7000.
> >
> > While debugging my application, with GDB, if a watchpoint hits when in a xenomai RT thread, the machine hangs.
> > If I connect the JTAG probe, I get core 1 halted with message "Synchronous Watchpoint", with PC being on the instruction that should have trigged the watchpoint. From that point, I can never get GDB or the app to continue. I can (using the JTAG debugger) hit continue, but it seems the app stays hung (even kill -9 does not terminate it and I have to reboot the target.
> >
> > Can anybody help ?
>
> Do you see the same issue with 5.10 or newer (Dovetail patch series), or
> with 4.19 (SLTS-based I-pipe)?
>

I can't tell for 5.10 as I have some custom driver for custom hardware that I did not port to dovetail/evl yet. The same is true for 4.19 (which lacks features I need) and I'm not sure I can easily test that. It was OK in 4.4 though

François

> Jan
>
> --
> Siemens AG, Technology
> Linux Expert Center
>


      reply	other threads:[~2023-11-09 14:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08 16:58 Watchpoints not being handled correctly on arm it seems François Legal
2023-11-09 11:22 ` Jan Kiszka
2023-11-09 14:38   ` François Legal [this message]

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=10237-654cef00-d-68598f00@146937372 \
    --to=devel@thom.fr.eu.org \
    --cc=jan.kiszka@siemens.com \
    --cc=xenomai@lists.linux.dev \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.