public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Don Breazeal <donb@codesourcery.com>
To: <gdb-patches@sourceware.org>
Subject: [PATCH v2] gdb.base/info-os.c: Clean up SysV IPC on error.
Date: Mon, 02 Feb 2015 22:37:00 -0000	[thread overview]
Message-ID: <1422916665-29806-1-git-send-email-donb@codesourcery.com> (raw)
In-Reply-To: <alpine.LFD.2.11.1501310504150.28301@eddie.linux-mips.org>

On 1/31/2015 3:55 AM, Maciej W. Rozycki wrote:
> Use `atexit' to run `ipc_cleanup' automagically instead maybe?  This way 
> you won't have to run the function manually at each exit point and also it 
> won't be missed on any future updates.

Maciej,
That makes sense to me.  Here is the updated patch.
Thanks!
--Don

We have noticed here that over time some of our test systems accumulate
stale System V IPC resources.  At least some of this is due to a GDB test
program, gdb.base/info-os.c.  The program doesn't clean up any allocated
IPC objects when an error occurs.  System V IPC objects will stay around
forever unless they are explicitly removed (or until a reboot).

This patch puts the IPC cleanup code into a function and calls atexit
so that the function will be called for any exit, not just successful
completion.

I looked at changing the SysV IPC key for allocating the IPC objects
to IPC_PRIVATE.  That would prevent a namespace conflict with the key.
However, the test needs to read the actual key number from the 'info os'
command output, and IPC_PRIVATE won't work for that.

One can clean up stale resources allocated by this test on Linux systems
by running 'ipcs' and looking for shared memory objects with keys in
the range 0xf55-0x133d, semaphore objects with keys in the range
0x1d04-20ec, and message queue objects in the range 0x14ae-0x1896.  Use
the 'ipcrm' command to delete the IPC objects.  Note that other programs
(like vncserver) use System V IPC, so make sure that the object is stale
before deleting it.

Tested on x86_64 Ubuntu.

OK?

thanks
--Don

gdb/testsuite/
2015-02-02  Don Breazeal  <donb@codesourcery.com>

	* gdb.base/info-os.c (shmid, semid, msqid): Make variables static
	and initialize them.
	(ipc_cleanup): New function.
	(main): Don't declare shmid, semid, and msqid.  Add a call to
	atexit so that we call ipc_cleanup on exit.

---
 gdb/testsuite/gdb.base/info-os.c | 22 ++++++++++++++++++----
 1 file changed, 18 insertions(+), 4 deletions(-)

diff --git a/gdb/testsuite/gdb.base/info-os.c b/gdb/testsuite/gdb.base/info-os.c
index ae2606a..8ceaaff 100644
--- a/gdb/testsuite/gdb.base/info-os.c
+++ b/gdb/testsuite/gdb.base/info-os.c
@@ -26,6 +26,22 @@
 
 static pthread_mutex_t mutex = PTHREAD_MUTEX_INITIALIZER;
 
+/* System V IPC identifiers.  */
+static int shmid = -1, semid = -1, msqid = -1;
+
+/* Delete any System V IPC resources that were allocated.  */
+
+static void
+ipc_cleanup (void)
+{
+  if (shmid >= 0)
+    shmctl (shmid, IPC_RMID, NULL);
+  if (semid >= 0)
+    semctl (semid, 0, IPC_RMID, NULL);
+  if (msqid >= 0)
+    msgctl (msqid, IPC_RMID, NULL);
+}
+
 void *
 thread_proc (void *args)
 {
@@ -38,7 +54,6 @@ main (void)
 {
   const int flags = IPC_CREAT | 0666;
   key_t shmkey = 3925, semkey = 7428, msgkey = 5294;
-  int shmid, semid, msqid;
   FILE *fd;
   pthread_t thread;
   struct sockaddr_in sock_addr;
@@ -47,6 +62,8 @@ main (void)
   socklen_t size;
   int status, try, retries = 1000;
 
+  atexit (ipc_cleanup);
+
   for (try = 0; try < retries; ++try)
     {
       shmid = shmget (shmkey, 4096, flags | IPC_EXCL);
@@ -135,9 +152,6 @@ main (void)
 
   /* Set breakpoint here.  */
 
-  shmctl (shmid, IPC_RMID, NULL);
-  semctl (semid, 0, IPC_RMID, NULL);
-  msgctl (msqid, IPC_RMID, NULL);
   fclose (fd);
   close (sock);
 
-- 
1.8.1.1

  reply	other threads:[~2015-02-02 22:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 20:16 [PATCH] gdb.base/info-os.c: clean " Don Breazeal
2015-01-31 22:22 ` Maciej W. Rozycki
2015-02-02 22:37   ` Don Breazeal [this message]
2015-02-03 15:32     ` [PATCH v2] gdb.base/info-os.c: Clean " Pedro Alves
2015-02-04 21:33       ` [commit] " Breazeal, Don

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=1422916665-29806-1-git-send-email-donb@codesourcery.com \
    --to=donb@codesourcery.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).