* Accessing shared memory
@ 2010-02-18 15:04 K. Jagielski
2010-02-18 17:40 ` Ine Ya
0 siblings, 1 reply; 2+ messages in thread
From: K. Jagielski @ 2010-02-18 15:04 UTC (permalink / raw)
To: gdb
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
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Accessing shared memory
2010-02-18 15:04 Accessing shared memory K. Jagielski
@ 2010-02-18 17:40 ` Ine Ya
0 siblings, 0 replies; 2+ messages in thread
From: Ine Ya @ 2010-02-18 17:40 UTC (permalink / raw)
To: K. Jagielski; +Cc: gdb
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
>
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2010-02-18 17:40 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2010-02-18 15:04 Accessing shared memory K. Jagielski
2010-02-18 17:40 ` Ine Ya
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox