public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Chris Markle <cmarkle@sendmail.com>
Cc: gdb@sources.redhat.com
Subject: Re: gcore command on 6.3 seems to generate smaller core than it should
Date: Tue, 13 Sep 2005 13:43:00 -0000	[thread overview]
Message-ID: <20050913134259.GA4829@nevyn.them.org> (raw)
In-Reply-To: <4326D389.9070709@sendmail.com>

On Tue, Sep 13, 2005 at 06:26:33AM -0700, Chris Markle wrote:
>   LOAD           0x016730 0x08048000 0x00000000 0x00000 0x0e000 R E 0x1
>   LOAD           0x024730 0x08056000 0x00000000 0x02000 0x02000 RWE 0x1
>   LOAD           0x026730 0x08058000 0x00000000 0xc4f000 0xc4f000 RWE 0x1

You've got the first three mappings here; 

> Here's a pmap of the process at the same time:
> 
> 31810:   [...]/java -server [...] -Xms1536m -Xmx1536m [...]
> 08056000      8K rwx--  /usr/local/sendmail/mm-2.1/jre15/bin/java
> 08058000  12604K rwx--    [ anon ]
> 44e00000  16384K rw-s-  /var/sendmail/mm/counters/countdb.data

it got to this one and stopped.

This is probably:

2005-05-23  Michael Snyder  <msnyder@redhat.com>

        From Nora Pan <qpan@mvista.com>
        * linux-nat.c (read_mapping): Don't stumble over entries in
        mapping that have name but zero inode.

Could you try a gdb CVS snapshot (6.3.50.*)?  If that doesn't work,
please post /proc/<pid>/maps.


-- 
Daniel Jacobowitz
CodeSourcery, LLC

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

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-13  3:51 Chris Markle
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 [this message]
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=20050913134259.GA4829@nevyn.them.org \
    --to=drow@false.org \
    --cc=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).