Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
comp.os.linux.embedded
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
Message from discussion memory protection in linux kernels
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark  
View profile  
 More options Oct 19 2012, 6:08 pm
Newsgroups: comp.unix.programmer, comp.os.linux.embedded
From: "Mark" <mark_cruzNOTFORS...@hotmail.com>
Date: Fri, 19 Oct 2012 18:08:30 -0400
Local: Fri, Oct 19 2012 6:08 pm
Subject: Re: memory protection in linux kernels
Print | View thread | Show original | Report this message | Find messages by this author

"Scott Lurndal" <sc...@slp53.sl.home> wrote in message

news:R2Wfs.9$726.7@fed11.iad...

>>> Turn on CONFIG_KDB and use kdb to set a watchpoint on the location being
>>> corrupted.   The processor will automatically stop and drop into kdb
>>> when the location is modified.

[skip]

>>Thank you. The target is ARM-based and runs the kernel 2.6.31.8, which has
>>only KGDB support, i.e. as I understand it allows to debug via rs232. What
>>is the difference with KDB?

> KDB is built in; it doesn't require a client on another machine like KGDB;
> but kgdb should work for your case since you've an earlier kernel.

After googling and reading I've set up kgdb over serial line, I can break
into the debugger (by stopping the kernel via /proc/sysrq-trigger) and
connect from host gdb, which is part of ARM toolchain.

Basically I have development board running embedded linux abd the driver I'm
debugging, and my PC with two connections to the board - serial and ethernet
(telnet session).

After I connect with host gdb to the target, I'm no longer able to do telnet
to the board, because the only way to reproduce the memory corruption is to
apply some configuration with user application on the board.

Is it expected or I'm doing something wrong, and there's a way to have alive
IP connection to the target *and* GDB session?

Mark


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google