From: freeman.zhang1992@gmail.com (Freeman Zhang)
To: kernelnewbies@lists.kernelnewbies.org
Subject: Debug Kernel Modules With KGDB
Date: Mon, 01 Dec 2014 19:02:25 +0800 [thread overview]
Message-ID: <547C4AC1.3050306@gmail.com> (raw)
In-Reply-To: <547C3AB4.6020506@cdac.in>
Hi Raghavendra,
Thanks for your reply, but `sudo` doesn't solve the problem :(
All the best!
Freeman Zhang
-------- Original Message --------
> On Monday 01 December 2014 03:26 PM, Freeman Zhang wrote:
>> Hi list,
>>
>> I've been trying to setup a debug environment for linux
>> kernel(v3.4,Android,ARM) with kgdb. It worked fine untill I tried to use
>> it to debug a module. Under the instruction from LDD, I add module debug
>> info in gdb with command:
>>
>> add-symbol-file test-module.ko address
>>
>> LDD uses `cat /sys/module/test-module/sections/.text` to get the address
>> where the module has been loaded. However, I got:
>>
>> 0x00000000
> Try reading the file as a root.
> $ sudo cat /sys/module/test-module/sections/.text
>>
>> When I use `lsmod`, I got:
>>
>> test-module 15278 0 - Live 0x00000000 (O)
>>
>> Why nothing but 0x00000000 ??
>>
>> So I have to do some research in kernel/module.c, and find out that
>> struct module -> module_core = 0xbf000000. But when I try these in gdb:
>>
>> add-symbol-file test-module.ko 0xbf000000
>> break one_of_my_function
>>
>> I got:
>>
>> Cannot access memory at address 0xbf002350
>>
>> :(
>> Could somebody help?
>>
>>
>> All the best!
>> Freeman Zhang
>>
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> Kernelnewbies mailing list
>> Kernelnewbies at kernelnewbies.org
>> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
>
> -------------------------------------------------------------------------------------------------------------------------------
>
> [ C-DAC is on Social-Media too. Kindly follow us at:
> Facebook: https://www.facebook.com/CDACINDIA & Twitter: @cdacindia ]
>
> This e-mail is for the sole use of the intended recipient(s) and may
> contain confidential and privileged information. If you are not the
> intended recipient, please contact the sender by reply e-mail and destroy
> all copies and the original message. Any unauthorized review, use,
> disclosure, dissemination, forwarding, printing or copying of this email
> is strictly prohibited and appropriate legal action will be taken.
> -------------------------------------------------------------------------------------------------------------------------------
>
>
>
>
>
> _______________________________________________
> Kernelnewbies mailing list
> Kernelnewbies at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
Url : http://lists.kernelnewbies.org/pipermail/kernelnewbies/attachments/20141201/0b502f4d/attachment.bin
next prev parent reply other threads:[~2014-12-01 11:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 9:56 Debug Kernel Modules With KGDB Freeman Zhang
2014-12-01 9:53 ` Raghavendra
2014-12-01 11:02 ` Freeman Zhang [this message]
2014-12-01 11:17 ` Raghavendra
2014-12-01 11:30 ` Freeman Zhang
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=547C4AC1.3050306@gmail.com \
--to=freeman.zhang1992@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.