All of lore.kernel.org
 help / color / mirror / Atom feed
From: Frederic Marmond <fmarmond@eprocess.fr>
To: linux-assembly@vger.kernel.org
Subject: Linear memory access, and register-modifier debugger
Date: Wed, 12 Jun 2002 12:36:17 +0200	[thread overview]
Message-ID: <3D072421.2060905@eprocess.fr> (raw)
In-Reply-To: 3D06ED6F.6090804@eprocess.fr

I'm sorry to send it again, but I had troubles with my suscribtion, 
obliged to re-suscribe to the list
So, (as the archive is down) i couldn't read any (if any) answer...
could you please re-post me answer if, if you have one...

by the way:
I'm looking for a debugger capable of changing  registers while 
executing the code (during a break-point for exemple), or/and best, 
modifying the code itself in memory.
for the code
brk        :08048081 6689c0                 mov  ax, ax
when steping to this breakpoint, filling the 6689c0 by 909090, to 
disable this wonderfull instruction, and step to the following! ;-)

ok, I know, there are 'pro' debuggers under windows.
I've use turboDebugger (borland, under dos) from my young time...
but now, under GNU/linux, I miss it!
(perhapse that under Linux, there is no bug at all, opposate to 
windows... ;-))


thanks in advance!
Fred

> Hi all,
>
> I'd like to access to a memory area on a mtd device, without having 
> compiling the mtd support in the kernel.
> (read a firmware info, on a embeded environment => kernel as small as 
> possible)
> Is there any isue?
>
> I mean:
> is the device mapped anywhere, or is it really invisible, if i don't 
> compile the mtd support?
> If it is visible (how can i check that point?) do you know if there is 
> any way to access it (like in flat mode, by a largest descriptor or 
> something...)?
>
>
> thanks for answers!
>
> Fred
>
>




      parent reply	other threads:[~2002-06-12 10:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-12  6:42 Linear memory access Frederic Marmond
2002-06-12  6:58 ` Konstantin Boldyshev
2002-06-12 10:36 ` Frederic Marmond [this message]

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=3D072421.2060905@eprocess.fr \
    --to=fmarmond@eprocess.fr \
    --cc=linux-assembly@vger.kernel.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.