Wednesday, August 24, 2005, 11:00:06 AM, Marco Pietrobono wrote:
> Il giorno mar, 23-08-2005 alle 18:05 -0600, Vitaliy Margolen ha scritto:
> [snip]
>> Unfortunately fixing NtQueryVirtualMemory, NtProtectVirtualMemory and others
>> is not that simple. Basically there are no way to do it from othe
Il giorno mar, 23-08-2005 alle 18:05 -0600, Vitaliy Margolen ha scritto:
[snip]
> Unfortunately fixing NtQueryVirtualMemory, NtProtectVirtualMemory and others
> is not that simple. Basically there are no way to do it from other processes.
> Ok, NtQueryVirtualMemory could be implemented some-what ea
Kuba Ober <[EMAIL PROTECTED]> writes:
> What are the problems with implementing those using SIGSTOP/SIGCONT and
> ptrace(2)?
The same problems that you'll have with signals, plus a few more
--
Alexandre Julliard
[EMAIL PROTECTED]
Wednesday, August 24, 2005, 6:20:40 AM, Kuba Ober wrote:
> On Tuesday 23 August 2005 20:05, Vitaliy Margolen wrote:
>> As of todays CVS Delphi 5 debugger is fixed.
>>
>> Well, ok, there are still some bugs. One is a minor bug (Module view
>> reports all modules as a project executable name), but
Vitaliy Margolen wrote:
As of todays CVS Delphi 5 debugger is fixed.
Unfortunately fixing NtQueryVirtualMemory, NtProtectVirtualMemory and others
is not that simple. Basically there are no way to do it from other processes.
Ok, NtQueryVirtualMemory could be implemented some-what easily usi
On Tuesday 23 August 2005 20:05, Vitaliy Margolen wrote:
> As of todays CVS Delphi 5 debugger is fixed.
>
> Well, ok, there are still some bugs. One is a minor bug (Module view
> reports all modules as a project executable name), but all exports are
> there. You can even try to disassemble them. Bu
As of todays CVS Delphi 5 debugger is fixed.
Well, ok, there are still some bugs. One is a minor bug (Module view reports all
modules as a project executable name), but all exports are there. You can even
try to disassemble them. But here is where the major problems start. Debugger
segfaults on th
