public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Chris Markle <cmarkle@sendmail.com>
To: gdb@sources.redhat.com
Subject: gcore command on 6.3 seems to generate smaller core than it should
Date: Tue, 13 Sep 2005 03:51:00 -0000	[thread overview]
Message-ID: <43264CB0.9090206@sendmail.com> (raw)

Folks,

Using GNU gdb 6.3 on 2.6.12.5 kernel (uname -a: Linux xxx.com 2.6.12.5 
#1 SMP Wed Aug 31 23:52:18 PDT 2005 i686 pentium4 i386 GNU/Linux), when 
I generate a core file of a Java process that is 1.9gb I get a 13mb (!) 
core file. Many addresses in that core are not accessible. There is no 
complaining from gcore about not enough space or other issues when I 
issue it, and ulimit show core blocks as unlimited. When I tried it on 
2.6.something-else with GNU gdb Red Hat Linux (5.3.90-0.20030710.40rh) I 
get a full very large core file.

Chris

             reply	other threads:[~2005-09-13  3:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  3:51 Chris Markle [this message]
2005-09-13  3:55 ` Daniel Jacobowitz
2005-09-13  5:58   ` Chris Markle
2005-09-13 12:40     ` Daniel Jacobowitz
2005-09-13 13:26       ` Chris Markle
2005-09-13 13:43         ` Daniel Jacobowitz
2005-09-14  5:55           ` Chris Markle
2005-09-14 15:29           ` Chris Markle

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=43264CB0.9090206@sendmail.com \
    --to=cmarkle@sendmail.com \
    --cc=gdb@sources.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).