public inbox for java-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: David Daney <david.s.daney@gmail.com>
To: java-patches@gcc.gnu.org
Cc: David Daney <ddaney@caviumnetworks.com>
Subject: [PATCH] Fix filename generation for out of memory dumps.
Date: Tue, 28 Jul 2009 04:18:00 -0000	[thread overview]
Message-ID: <4A6E7C29.1010300@gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 431 bytes --]

As noted here:

http://gcc.gnu.org/ml/java/2009-07/msg00067.html

The filename generation in the out of memory dumps is a bit screwed up.  
This patch restores it to its intended state.

Bootstrapped and regression tested on x86_64-pc-linux-gnu with no 
regressions.

OK to commit?

2009-07-28  David Daney  <ddaney@caviumnetworks.com>

    * gnu/gcj/util/natGCInfo.cc (nomem_handler): Use oomDumpName as
    dump file name base.


[-- Attachment #2: gcinfo.patch --]
[-- Type: text/plain, Size: 527 bytes --]

Index: gnu/gcj/util/natGCInfo.cc
===================================================================
--- gnu/gcj/util/natGCInfo.cc	(revision 150090)
+++ gnu/gcj/util/natGCInfo.cc	(working copy)
@@ -407,7 +407,7 @@ nomem_handler(size_t size)
   if (oomDumpName)
     {
       char temp[strlen(oomDumpName) + 20];
-      sprintf(temp, "%s%03d", temp, GC_dump_count++);
+      sprintf(temp, "%s%03d", oomDumpName, GC_dump_count++);
       printf("nomem_handler(%zd) called\n", size);
       gc_ok--;
       GC_enumerator x(temp);

             reply	other threads:[~2009-07-28  4:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-28  4:18 David Daney [this message]
2009-07-28  8:31 ` Andrew Haley
2009-07-28  8:33 ` Andrew Haley

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=4A6E7C29.1010300@gmail.com \
    --to=david.s.daney@gmail.com \
    --cc=ddaney@caviumnetworks.com \
    --cc=java-patches@gcc.gnu.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).