From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-return-36910-listarch-gdb=sources.redhat.com@sourceware.org>
Received: (qmail 16964 invoked by alias); 18 Feb 2010 17:40:06 -0000
Received: (qmail 16956 invoked by uid 22791); 18 Feb 2010 17:40:05 -0000
X-SWARE-Spam-Status: No, hits=-2.0 required=5.0 	tests=BAYES_00,SARE_MSGID_LONG40,SPF_PASS
X-Spam-Check-By: sourceware.org
Received: from mail-fx0-f215.google.com (HELO mail-fx0-f215.google.com) (209.85.220.215)     by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Thu, 18 Feb 2010 17:39:59 +0000
Received: by fxm7 with SMTP id 7so9406813fxm.8         for <gdb@sourceware.org>; Thu, 18 Feb 2010 09:39:56 -0800 (PST)
MIME-Version: 1.0
Received: by 10.216.86.83 with SMTP id v61mr333696wee.80.1266514795082; Thu,  	18 Feb 2010 09:39:55 -0800 (PST)
In-Reply-To: <3818d4521002180704w2b51e4fl1144408c2ef70724@mail.gmail.com>
References: <3818d4521002180704w2b51e4fl1144408c2ef70724@mail.gmail.com>
Date: Thu, 18 Feb 2010 17:40:00 -0000
Message-ID: <7b8592a1002180939y381c41d7nc37ca8677dcfa764@mail.gmail.com>
Subject: Re: Accessing shared memory
From: Ine Ya <ineyaa@gmail.com>
To: "K. Jagielski" <gilvannco@gmail.com>
Cc: gdb@sourceware.org
Content-Type: text/plain; charset=ISO-8859-1
X-IsSubscribed: yes
Mailing-List: contact gdb-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb.sourceware.org>
List-Subscribe: <mailto:gdb-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb/>
List-Post: <mailto:gdb@sourceware.org>
List-Help: <mailto:gdb-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: gdb-owner@sourceware.org
X-SW-Source: 2010-02/txt/msg00128.txt.bz2

Hi,

for coredumps:
check /proc/<pid>/maps and find out what flags this area has.
Then you can try to change the flags, so vma_dump_size() would not
return 0, or change this function for your needs and rebuild the
kernel.
http://lxr.linux.no/#linux+v2.6.32/fs/binfmt_elf.c#L1150

Hope this helps (I haven't tried this before),
Ineya

On Thu, Feb 18, 2010 at 4:04 PM, K. Jagielski <gilvannco@gmail.com> wrote:
> Hello,
> I'm allocating a memory block inside a kernel module and then I share
> it with an user space application through mmap(). I have two problems:
> 1. The memory isn't written into core files
> 2. The memory isn't accessible during "runtime" debugging (the result
> of "attach" command & similar)
>
> How to solve those issues?
>
> Regards,
> Krzysztof
>