unofficial mirror of meta@public-inbox.org
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: meta@public-inbox.org
Subject: [PATCH] xap_helper: test cleanup + throw support in C++
Date: Sat, 16 Sep 2023 13:10:52 +0000	[thread overview]
Message-ID: <20230916131052.M335143@dcvr> (raw)
In-Reply-To: <20230909120142.1041752-7-e@80x24.org>

Eric Wong <e@80x24.org> wrote:
> In case somebody reviewing this code gets curious.

And just in case we encounter other C++ implementations:
-------8<-------
Subject: [PATCH] xap_helper: test cleanup + throw support in C++

We need to ensure whatever C++ compiler gets used supports this
GNU extension as we expect it to.  clang 13 and 14 and g++ 10
all work as we expect it to.
---
 side note: sadly, longjmp/siglongjmp(3) in POSIX does not trigger
 __cleanup__

 lib/PublicInbox/xap_helper.h | 23 +++++++++++++++++++----
 1 file changed, 19 insertions(+), 4 deletions(-)

diff --git a/lib/PublicInbox/xap_helper.h b/lib/PublicInbox/xap_helper.h
index 2322d062..377ff45a 100644
--- a/lib/PublicInbox/xap_helper.h
+++ b/lib/PublicInbox/xap_helper.h
@@ -578,12 +578,27 @@ static bool cmd_dump_roots(struct req *req)
 	return true;
 }
 
-// internal usage only
+// for test usage only, we need to ensure the compiler supports
+// __cleanup__ when exceptions are thrown
+struct inspect { struct req *req; };
+
+static void inspect_ensure(struct inspect *x)
+{
+	fprintf(x->req->fp[0], "pid=%d has_threadid=%d",
+		(int)getpid(), has_threadid(x->req->srch) ? 1 : 0);
+}
+
 static bool cmd_test_inspect(struct req *req)
 {
-	fprintf(req->fp[0], "pid=%d has_threadid=%d",
-		(int)getpid(), has_threadid(req->srch) ? 1 : 0);
-	return true;
+	__attribute__((__cleanup__(inspect_ensure))) struct inspect x;
+	x.req = req;
+	try {
+		throw Xapian::InvalidArgumentError("test");
+	} catch (Xapian::InvalidArgumentError) {
+		return true;
+	}
+	fputs("this should not be printed", req->fp[0]);
+	return false;
 }
 
 #define CMD(n) { .fn_len = sizeof(#n) - 1, .fn_name = #n, .fn = cmd_##n }

  reply	other threads:[~2023-09-16 13:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-09 12:01 [PATCH 0/8] NetBSD-related updates Eric Wong
2023-09-09 12:01 ` [PATCH 1/8] Makefile.PL: check `getconf NPROCESSORS_ONLN', too Eric Wong
2023-09-09 12:01 ` [PATCH 2/8] ipc: define _SC_NPROCESSORS_ONLN for NetBSD Eric Wong
2023-09-09 12:01 ` [PATCH 3/8] ci/run.sh: parameterize BUILD_JOBS TEST_JOBS and TEST_TARGET Eric Wong
2023-09-09 12:01 ` [PATCH 4/8] ci/profiles: rewrite in Perl Eric Wong
2023-09-09 21:14   ` [SQUASH] manifest update Eric Wong
2023-09-09 12:01 ` [PATCH 5/8] update CI helper scripts for NetBSD and `pkgin' Eric Wong
2023-09-09 12:01 ` [PATCH 6/8] xap_helper: note __cleanup__ works with C++ exceptions Eric Wong
2023-09-16 13:10   ` Eric Wong [this message]
2023-09-09 12:01 ` [PATCH 7/8] xap_helper: use _OPENBSD_SOURCE on NetBSD for reallocarray Eric Wong
2023-09-09 12:01 ` [PATCH 8/8] xap_helper: clamp workers to USHRT_MAX Eric Wong

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

  List information: https://public-inbox.org/README

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230916131052.M335143@dcvr \
    --to=e@80x24.org \
    --cc=meta@public-inbox.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).