From: "Michael Kerrisk" <mtk.manpages@googlemail.com>
To: "Philippe De Muyter" <phdm@macqel.be>
Cc: "Michael Kerrisk" <mtk.manpages@gmail.com>,
linux-kernel@vger.kernel.org,
libdc1394-devel@lists.sourceforge.net,
hidehiro.kawai.ez@hitachi.com
Subject: Re: mmap'ed memory in core files ?
Date: Wed, 2 Jul 2008 12:58:05 +0200 [thread overview]
Message-ID: <cfd18e0f0807020358k317575c6ra0187428098f0160@mail.gmail.com> (raw)
In-Reply-To: <20080702105027.GA1111@frolo.macqel>
[CC+= hidehiro.kawai.ez@hitachi.com]
On Wed, Jul 2, 2008 at 12:50 PM, Philippe De Muyter <phdm@macqel.be> wrote:
> Hi Michael,
>
> On Tue, Jul 01, 2008 at 08:16:11PM +0200, Michael Kerrisk wrote:
>> On 7/1/08, Philippe De Muyter <phdm@macqel.be> wrote:
>> > Hello everybody,
>> >
>> > I develop video acquisition software using the video1394 interface.
>> > The images grabbed by the camera and iee1394 bus are kept in kernel
>> > memory and made available to the user program through a mmap call done
>> > in the libdc1394 library :
>> >
>> > dma_ring_buffer= mmap(0, vmmap.nb_buffers * vmmap.buf_size,
>> > PROT_READ|PROT_WRITE,MAP_SHARED, craw->capture.dma_fd, 0);
>> >
>> > Sometimes, my program crashes and produces a core file :) It seems to
>> > me that the core file does not contain the mmap'ed memory and hence
>> > I cannot replay my program with the same image for debugging purpose.
>> >
>> > Is it possible to configure the kernel through /proc, or through the mmap
>> > system call to have that mmapped segment in the core file, or do I need
>> > to modify the kernel itself to obtain the behaviour I want ? If I
>> > need to modify the kernel, can some kind soul provide me some pointers ?
>>
>>
>> Have a look at the section "Controlling which mappings are written to
>> the core dump" in a recent core.5 man page:
>> http://www.kernel.org/doc/man-pages/online/pages/man5/core.5.html
>
> thanks for the info. I didn't know about /proc/PID/coredump_filter.
>
> that part was promising :
>
> bit 2 Dump file-backed private mappings.
> bit 3 Dump file-backed shared mappings.
>
> The default value of coredump_filter is 0x3; this reflects traditional
> Linux behavior and means that only anonymous memory segments are dumped.
>
> Unfortunately, the part that applies to me (I have tested it) is the next one :
>
> Memory-mapped I/O pages such as frame buffer are never dumped, [...],
> regardless of the coredump_filter value.
>
> Is that a design decision, or a mere finding of the way it is implemented
> now ?
>
> So, back to my original question :
>
> Can some kind soul provide me some pointers to the way I should modify
> the kernel to make the inclusion of the video1394 mmapped segment in
> core files possible ?
Perhaps Hidehiro, who wrote the coredump_filter feature, can provide insight.
Cheers,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
man-pages online: http://www.kernel.org/doc/man-pages/online_pages.html
Found a bug? http://www.kernel.org/doc/man-pages/reporting_bugs.html
next prev parent reply other threads:[~2008-07-02 10:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-01 13:21 Philippe De Muyter
2008-07-01 18:16 ` Michael Kerrisk
2008-07-01 21:44 ` Bron Gondwana
2008-07-02 5:14 ` Michael Kerrisk
2008-07-02 6:35 ` Rob Mueller
2008-07-02 11:07 ` Andi Kleen
2008-07-02 11:52 ` Bron Gondwana
2008-07-02 10:50 ` Philippe De Muyter
2008-07-02 10:58 ` Michael Kerrisk [this message]
2008-07-02 11:04 ` Philippe De Muyter
2008-07-02 12:24 ` Stefan Richter
2008-07-02 13:16 ` Philippe De Muyter
2008-07-03 3:51 ` Hidehiro Kawai
2008-07-03 9:22 ` Philippe De Muyter
2008-07-04 5:50 ` Hidehiro Kawai
2008-07-04 6:33 ` Stefan Richter
2008-07-04 11:25 ` Philippe De Muyter
2008-07-04 14:29 ` Hugh Dickins
2008-07-04 11:13 ` Philippe De Muyter
2008-07-03 9:37 ` Philippe De Muyter
2008-07-03 16:52 ` [PATCH] ieee1394 : dump mmapped video1394 buffers in core files Philippe De Muyter
2008-07-04 18:33 ` Stefan Richter
2008-07-04 20:49 ` Philippe De Muyter
2008-07-02 13:30 ` mmap'ed memory in core files ? Christoph Hellwig
2008-07-02 11:01 ` Philippe De Muyter
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=cfd18e0f0807020358k317575c6ra0187428098f0160@mail.gmail.com \
--to=mtk.manpages@googlemail.com \
--cc=hidehiro.kawai.ez@hitachi.com \
--cc=libdc1394-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=phdm@macqel.be \
/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
all inboxes | Powered by JetHome®