From: Doug Evans <dje@google.com>
To: Tom Tromey <tromey@redhat.com>
Cc: gdb-patches@sourceware.org, cmtice@google.com
Subject: Re: [patch] handle nested exceptions
Date: Thu, 15 Dec 2011 18:45:00 -0000 [thread overview]
Message-ID: <CADPb22RsvkUnGwMwosU7-5UNayqeC1ypAYkxpw7uLSt61pKpPw@mail.gmail.com> (raw)
In-Reply-To: <m3ty516fvj.fsf@fleche.redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1224 bytes --]
On Thu, Dec 15, 2011 at 6:58 AM, Tom Tromey <tromey@redhat.com> wrote:
>>>>>> "Doug" == Doug Evans <dje@google.com> writes:
>
> Doug> I will check this in in a few days if there are no objections.
> Doug> 2011-12-14 Doug Evans <dje@google.com>
>
> Doug> * exceptions.c (catcher_list_size): New function.
> Doug> (last_message): Delete.
> Doug> (exception_messages, exception_messages_size): New static globals.
> Doug> (throw_it): Use exception_messages array to handle nested calls.
>
> It seems good to me.
>
> It was a little hard to understand why this was the right approach.
> Actually I am not 100% sure I have convinced myself.
> I think a comment explaining the motivating scenario would help.
The motivating scenario is when we call throw_it instead a cleanup due
to an earlier throw_it.
[Actually, for the case at hand there were multiple calls to throw_it
during the cleanup.]
How's this?
2011-12-15 Doug Evans <dje@google.com>
* exceptions.c (catcher_list_size): New function.
(last_message): Delete.
(exception_messages, exception_messages_size): New static globals.
(throw_it): Use exception_messages array to handle nested calls.
[-- Attachment #2: gdb-111215-nested-throw-it-3.patch.txt --]
[-- Type: text/plain, Size: 3258 bytes --]
2011-12-15 Doug Evans <dje@google.com>
* exceptions.c (catcher_list_size): New function.
(last_message): Delete.
(exception_messages, exception_messages_size): New static globals.
(throw_it): Use exception_messages array to handle nested calls.
Index: exceptions.c
===================================================================
RCS file: /cvs/src/src/gdb/exceptions.c,v
retrieving revision 1.48
diff -u -p -r1.48 exceptions.c
--- exceptions.c 26 Aug 2011 21:45:22 -0000 1.48
+++ exceptions.c 15 Dec 2011 17:58:51 -0000
@@ -68,6 +68,22 @@ struct catcher
/* Where to go for throw_exception(). */
static struct catcher *current_catcher;
+/* Return length of current_catcher list. */
+
+static int
+catcher_list_size (void)
+{
+ int size;
+ struct catcher *catcher;
+
+ for (size = 0, catcher = current_catcher;
+ catcher != NULL;
+ catcher = catcher->prev)
+ ++size;
+
+ return size;
+}
+
EXCEPTIONS_SIGJMP_BUF *
exceptions_state_mc_init (volatile struct gdb_exception *exception,
return_mask mask)
@@ -220,8 +236,6 @@ throw_exception (struct gdb_exception ex
EXCEPTIONS_SIGLONGJMP (current_catcher->buf, exception.reason);
}
-static char *last_message;
-
void
deprecated_throw_reason (enum return_reason reason)
{
@@ -359,23 +373,53 @@ print_any_exception (struct ui_file *fil
}
}
+/* A stack of exception messages.
+ This is needed to handle nested calls to throw_it: we don't want to
+ xfree space for a message before it's used.
+ This can happen if we throw an exception during a cleanup:
+ An outer TRY_CATCH may have an exception message it wants to print,
+ but while doing cleanups further calls to throw_it are made.
+
+ This is indexed by the size of the current_catcher list.
+ It is a dynamically allocated array so that we don't care how deeply
+ GDB nests its TRY_CATCHs. */
+static char **exception_messages;
+
+/* The number of currently allocated entries in exception_messages. */
+static int exception_messages_size;
+
static void ATTRIBUTE_NORETURN ATTRIBUTE_PRINTF (3, 0)
throw_it (enum return_reason reason, enum errors error, const char *fmt,
va_list ap)
{
struct gdb_exception e;
char *new_message;
+ int depth = catcher_list_size ();
- /* Save the message. Create the new message before deleting the
- old, the new message may include the old message text. */
+ gdb_assert (depth > 0);
+
+ /* Note: The new message may use an old message's text. */
new_message = xstrvprintf (fmt, ap);
- xfree (last_message);
- last_message = new_message;
+
+ if (depth > exception_messages_size)
+ {
+ int old_size = exception_messages_size;
+
+ exception_messages_size = depth + 10;
+ exception_messages = (char **) xrealloc (exception_messages,
+ exception_messages_size
+ * sizeof (char *));
+ memset (exception_messages + old_size, 0,
+ (exception_messages_size - old_size) * sizeof (char *));
+ }
+
+ xfree (exception_messages[depth - 1]);
+ exception_messages[depth - 1] = new_message;
/* Create the exception. */
e.reason = reason;
e.error = error;
- e.message = last_message;
+ e.message = new_message;
/* Throw the exception. */
throw_exception (e);
next prev parent reply other threads:[~2011-12-15 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 23:21 Doug Evans
2011-12-15 15:04 ` Tom Tromey
2011-12-15 18:45 ` Doug Evans [this message]
2011-12-15 21:37 ` Tom Tromey
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=CADPb22RsvkUnGwMwosU7-5UNayqeC1ypAYkxpw7uLSt61pKpPw@mail.gmail.com \
--to=dje@google.com \
--cc=cmtice@google.com \
--cc=gdb-patches@sourceware.org \
--cc=tromey@redhat.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