From: "Pierre Muller" <pierre.muller@ics-cnrs.unistra.fr>
To: <gdb-patches@sourceware.org>
Subject: [RFA/ARI fix] Remove use of abort function in common/buffer.c
Date: Tue, 22 May 2012 09:17:00 -0000 [thread overview]
Message-ID: <001201cd37fb$b06a7c20$113f7460$@muller@ics-cnrs.unistra.fr> (raw)
ARI clearly states that abort function
should never be used, and to use internal_error
instead.
I first suspected that this was related to missing declarations in
common directory, but internal_error does
exist there also.
Finally, looking at common/buffer.c source, I found that
gdb_assert was probably a better fit here
(the macro does call internal_error).
Is this patch OK or what else should we use here?
Pierre Muller
GDB pascal language maintainer
2012-05-22 Pierre Muller <muller@ics.u-strasbg.fr>
* common/buffer.c (buffer_grow): ARI fix: Replace abort
function call by gdb_assert macro use.
Index: common/buffer.c
===================================================================
RCS file: /cvs/src/src/gdb/common/buffer.c,v
retrieving revision 1.3
diff -u -p -r1.3 buffer.c
--- common/buffer.c 11 May 2012 22:24:22 -0000 1.3
+++ common/buffer.c 22 May 2012 09:10:27 -0000
@@ -23,6 +23,7 @@
#include "defs.h"
#endif
+#include "gdb_assert.h"
#include "xml-utils.h"
#include "buffer.h"
@@ -47,8 +48,7 @@ buffer_grow (struct buffer *buffer, cons
while (buffer->used_size + size > new_buffer_size)
new_buffer_size *= 2;
new_buffer = xrealloc (buffer->buffer, new_buffer_size);
- if (!new_buffer)
- abort ();
+ gdb_assert (new_buffer);
memcpy (new_buffer + buffer->used_size, data, size);
buffer->buffer = new_buffer;
buffer->buffer_size = new_buffer_size;
next reply other threads:[~2012-05-22 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 9:17 Pierre Muller [this message]
[not found] <4fbb59b7.44e2440a.48c4.ffffab13SMTPIN_ADDED@mx.google.com>
2012-05-22 9:34 ` Pedro Alves
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='001201cd37fb$b06a7c20$113f7460$@muller@ics-cnrs.unistra.fr' \
--to=pierre.muller@ics-cnrs.unistra.fr \
--cc=gdb-patches@sourceware.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