public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi@argo.co.il>
To: 7eggert@nurfuerspam.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] WTF is VLI?
Date: Fri, 19 Nov 2004 01:44:30 +0200	[thread overview]
Message-ID: <419D33DE.2080100@argo.co.il> (raw)
In-Reply-To: <E1CUr14-0000oQ-00@be1.7eggert.dyndns.org>

Bodo Eggert wrote:

>Avi Kivity wrote:
>
>  
>
>>for (offset = 0; offset < max_instr_len; ++offset) {
>>    create_object_file(code + offset, len - offset);
>>    disassemble();
>>    if (disassembly_includes_eip())
>>    
>>
>
>
>Will fail for
>
>movl eax,cc000000 ;or something similar, you get the point
>*EIP here*
>
>and result in
>
>INT3
>  
>
no, it will start at lower offsets first and see the movl.

of course, there is a chance that it will get confused (by even earlier 
partial code), but it will usually be better than the current method and 
it will never be confused at or above eip (same as current method).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.


  reply	other threads:[~2004-11-18 23:50 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <fa.inbtt12.195ed02@ifi.uio.no>
     [not found] ` <fa.cg6f09j.ji89hv@ifi.uio.no>
2004-11-18 18:28   ` [PATCH] WTF is VLI? Bodo Eggert
2004-11-18 23:44     ` Avi Kivity [this message]
2004-11-11 21:05 Hugh Dickins
2004-11-11 21:10 ` Dave Jones
2004-11-12 23:26   ` Horst von Brand
2004-11-15 21:18     ` Hugh Dickins
2004-11-16  6:00       ` Keith Owens
2004-11-16  9:56         ` Hugh Dickins
2004-11-17  5:55           ` Keith Owens
2004-11-18 15:47             ` Avi Kivity
2004-11-18 18:08               ` Horst von Brand
2004-11-18 23:38                 ` Avi Kivity
2004-11-21  3:58               ` Keith Owens
2004-11-11 21:14 ` Andrew Morton

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=419D33DE.2080100@argo.co.il \
    --to=avi@argo.co.il \
    --cc=7eggert@nurfuerspam.de \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox