From: "Yan, Zhiyong" <Zhiyong.Yan@windriver.com>
To: Bruno Larsen <blarsen@redhat.com>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Cc: "tom@tromey.com" <tom@tromey.com>
Subject: RE: [PATCH] [patch] gdbserver assert error on arm platform
Date: Tue, 20 Jun 2023 08:08:52 +0000 [thread overview]
Message-ID: <DS0PR11MB64479A8908E9B751C901BD2AE75CA@DS0PR11MB6447.namprd11.prod.outlook.com> (raw)
In-Reply-To: <50177562-7c96-ec44-5452-b5d3c5ae6a0e@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 3721 bytes --]
Hi Bruno,
The test case is attached into https://sourceware.org/bugzilla/show_bug.cgi?id=30387. Please look for "Luis Machado 2023-05-02 14:17:40 UTC" in Bugzilla comments, you can see Luis already produced this issue.
I copy Produce step below, test app and gdb script can be found in the attachment.
Produce step (This issue can only be produced on arm platform):
(1) tar xvf gdbserver-test-app.tar on a host which can do arm-cross compile.
(2) In osm.service, modify ExecStart path according to your running environment.
(3) make
(4) Please refer to "make install", install osm systemd service on target board.
[On target board]
systemctl daemon-reload
systemctl start osm
gdbserver --debug --debug-format=all --remote-debug --event-loop-debug --once --attach :1234 $(pgrep osm)
[On pc host]
your-arm-gdb ./osm(this is test app build out as above) -x ~/gdbx2
gdbx2 can be found in the attachment, please modify target-remote pointing to your target board's gdbserver in gdbx2.
When gdb executes gdbx2, gdbserver will assert on target board.
-----Original Message-----
From: Bruno Larsen <blarsen@redhat.com>
Sent: Tuesday, June 20, 2023 3:36 PM
To: Yan, Zhiyong <Zhiyong.Yan@windriver.com>; gdb-patches@sourceware.org
Cc: tom@tromey.com
Subject: Re: [PATCH] [patch] gdbserver assert error on arm platform
CAUTION: This email comes from a non Wind River email account!
Do not click links or open attachments unless you recognize the sender and know the content is safe.
Hi Zhiyong,
Kevin has posted a review back in may 11th:
https://inbox.sourceware.org/gdb-patches/20230511140407.0a0977fb@f37-zws-nv/
--
Cheers,
Bruno
On 19/06/2023 03:50, Yan, Zhiyong wrote:
> Hi,
> Did this patch get a chance of review ?
>
> Thanks!
> Zhiyong
>
>
>
> -----Original Message-----
> From: zhiyong.yan@windriver.com <zhiyong.yan@windriver.com>
> Sent: Thursday, May 11, 2023 2:20 PM
> To: gdb-patches@sourceware.org
> Cc: tom@tromey.com; Yan, Zhiyong <Zhiyong.Yan@windriver.com>
> Subject: [PATCH] [patch] gdbserver assert error on arm platform
>
> From: Zhiyong Yan <zhiyong.yan@windriver.com>
>
> Bugzilla 30387 has given the steps of producing this issue on arm platform.
> Gdb should not assume pending threads always generate “a non-gdbserver trap event”, a “Signal 17” event could happen.
> Now that resume_stopped_resumed_lwps() -> may_hw_step() assumes that the break point must already exist, resume_one_thread() should ensure the software breaking point is installed although the thread is pending.
>
> LINK: https://sourceware.org/bugzilla/show_bug.cgi?id=30387
>
> Signed-off-by: Zhiyong Yan zhiyong.yan@windriver.com
> ---
> gdbserver/linux-low.cc | 12 ++++++++++--
> 1 file changed, 10 insertions(+), 2 deletions(-)
>
> diff --git a/gdbserver/linux-low.cc b/gdbserver/linux-low.cc index e6a39202a98..543daf66376 100644
> --- a/gdbserver/linux-low.cc
> +++ b/gdbserver/linux-low.cc
> @@ -4670,8 +4670,16 @@ linux_process_target::resume_one_thread (thread_info *thread,
>
> proceed_one_lwp (thread, NULL);
> }
> - else
> - threads_debug_printf ("leaving LWP %ld stopped", lwpid_of (thread));
> + else{
> + threads_debug_printf ("leaving LWP %ld stopped", lwpid_of (thread));
> + if(thread->last_resume_kind == resume_step){
> + /*
> + * If resume_step is required by GDB, install single-step breakpoint.
> + */
> + if (supports_software_single_step())
> + install_software_single_step_breakpoints (lwp);
> + }
> + }
>
> thread->last_status.set_ignore ();
> lwp->resume = NULL;
> --
> 2.25.1
>
[-- Attachment #2: gdbserver-test-app.tar --]
[-- Type: application/x-tar, Size: 10240 bytes --]
[-- Attachment #3: gdbx2 --]
[-- Type: application/octet-stream, Size: 356 bytes --]
# gdbserver --once --attach :1234 $(pgrep eqptCntrl)
set pagination off
#target remote 128.224.176.94:1234
target remote 128.224.178.123:1234
#set logging file pr29742-host.log
#set logging enabled
#set debug remote 1
#set debug remote-packet-max-chars unlimited
handle SIG32 nostop noprint
handle SIGSTOP nostop noprint
b lpudated.c:92
c
n
n
n
n
n
next prev parent reply other threads:[~2023-06-20 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-11 6:20 zhiyong.yan
2023-05-11 21:04 ` Kevin Buettner
2023-06-19 1:50 ` Yan, Zhiyong
2023-06-20 7:35 ` Bruno Larsen
2023-06-20 8:08 ` Yan, Zhiyong [this message]
2023-06-22 1:44 ` Kevin Buettner
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=DS0PR11MB64479A8908E9B751C901BD2AE75CA@DS0PR11MB6447.namprd11.prod.outlook.com \
--to=zhiyong.yan@windriver.com \
--cc=blarsen@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=tom@tromey.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).