From: Luis Machado <luis.machado@arm.com>
To: Chris Packham <judge.packham@gmail.com>,
GDB Mailing list <gdb@sourceware.org>
Subject: Re: Problems interrupting remote target on powerpc
Date: Fri, 28 Apr 2023 10:18:51 +0100 [thread overview]
Message-ID: <b84169f8-cfff-0b99-599c-909ae02ab9e4@arm.com> (raw)
In-Reply-To: <CAFOYHZA2t83aa1M=M0t3KA58sj+9+s_mvj9Nr-riE4XCD5A6BQ@mail.gmail.com>
On 4/28/23 10:14, Chris Packham via Gdb wrote:
> On Thu, 27 Apr 2023, 4:55 PM Chris Packham, <judge.packham@gmail.com> wrote:
>
>> Hi GDB,
>>
>> I've had a few users report to me issues with interrupting a running
>> process after continuing when attached to a remote gdbserver running
>> on a powerpc target. Everything seems to work properly on arm and
>> aarch64 so there might be some powerpc or big-endian specific issue
>> lurking.
>>
>> The gdbserver version we're currently using is from gdb-11.2 built
>> from source and most users have gdb-multiarch 12.1 from ubuntu 22.04
>> (some might still be using gdb-multiarch 10.2 from a PPA).
>>
>> Does this ring any bells for anyone? I'm going to try and get hold of
>> a powerpc target to test with to see if I can reproduce it for myself.
>>
>> Thanks,
>> Chris
>>
>
> Did some digging of my own I can report that indeed things aren't working
> well for powerpc. I tried updating gdbserver to 12.1 and 13.1. 12.1 was
> much the same as 11.2. 13.1 reported that it was unable to send sigkill
> when processing the interrupt command. 13.1 also seems not to be able to
> respond to the 'info os processes' command from the gdb client
>
>>
What sort of behavior/output do you see?
next prev parent reply other threads:[~2023-04-28 9:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-27 4:55 Chris Packham
2023-04-28 9:14 ` Chris Packham
2023-04-28 9:18 ` Luis Machado [this message]
2023-04-28 9:38 ` Chris Packham
2023-04-28 9:40 ` Luis Machado
2023-04-28 11:25 ` Chris Packham
2023-04-28 13:02 ` Luis Machado
2023-04-28 14:05 ` Joel Brobecker
2023-05-01 5:30 ` Chris Packham
2023-05-01 21:20 ` Chris Packham
2023-05-02 12:46 ` Tom Tromey
2023-05-02 12:55 ` Luis Machado
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=b84169f8-cfff-0b99-599c-909ae02ab9e4@arm.com \
--to=luis.machado@arm.com \
--cc=gdb@sourceware.org \
--cc=judge.packham@gmail.com \
/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).