From: Tom Tromey <tom@tromey.com>
To: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org>
Cc: Pedro Alves <pedro@palves.net>, Andrew Burgess <aburgess@redhat.com>
Subject: Re: [PATCH 1/2] gdb: only allow one of thread or task on breakpoints or watchpoints
Date: Sun, 12 Feb 2023 15:58:37 -0700 [thread overview]
Message-ID: <87v8k6ebj6.fsf@tromey.com> (raw)
In-Reply-To: <878rh3v3dx.fsf@redhat.com> (Andrew Burgess via Gdb-patches's message of "Sun, 12 Feb 2023 05:50:18 +0000")
Andrew> I gave the test a more descriptive name, and pushed both patches in this
Andrew> series.
I didn't bisect but I suspect this caused:
guile (set-breakpoint-thread! bp 1)
ERROR: In procedure set-breakpoint-thread!:
ERROR: In procedure gdbscm_set_breakpoint_thread_x: cannot set both task and thread attributes
Error while executing Scheme code.
(gdb) FAIL: gdb.ada/tasks.exp: attempt to set thread, but expect an error
and
guile (set-breakpoint-task! bp 1)
ERROR: In procedure set-breakpoint-task!:
ERROR: In procedure gdbscm_set_breakpoint_task_x: cannot set both task and thread attributes
Error while executing Scheme code.
(gdb) FAIL: gdb.ada/tasks.exp: attempt to set task, but expect an error
Tom
next prev parent reply other threads:[~2023-02-12 22:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 15:16 [PATCH 0/2] Prevent combining 'task' and 'thread' keywords Andrew Burgess
2023-02-08 15:16 ` [PATCH 1/2] gdb: only allow one of thread or task on breakpoints or watchpoints Andrew Burgess
2023-02-08 15:52 ` Eli Zaretskii
2023-02-08 18:10 ` Pedro Alves
2023-02-12 5:50 ` Andrew Burgess
2023-02-12 22:58 ` Tom Tromey [this message]
2023-02-13 11:26 ` Andrew Burgess
2023-02-08 15:16 ` [PATCH 2/2] gdb: use -1 for breakpoint::task default value Andrew Burgess
2023-02-08 18:10 ` Pedro Alves
2023-02-12 7:23 ` Andrew Burgess
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=87v8k6ebj6.fsf@tromey.com \
--to=tom@tromey.com \
--cc=aburgess@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=pedro@palves.net \
/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).