flat assembler
Message board for the users of flat assembler.
Index
> IDE Development > Fresh 1.0.06 pre-alpha Goto page Previous 1, 2, 3 |
Author |
|
scientica 27 Aug 2003, 14:07
Just one comment, I think that the debugger should be able to crash wothout taking donw the entire IDE, or atleast save all project files (and sak for other files to be save) - so that the risc of lossing data is minimal.
As for point 5, you don't mean follow every instruction in GUI when "running" the exe? (It would slow down things *a lot*, better have two run-modes, run - don't show the current execution point (update GUI when the app stops/is stopped), follow/trace - the slow mode that shows every instruciton step in the debugger GUI). Of couse stepping should be allowed. And I'd like to see an possibillity to "skip" debugging of system dlls (Olly has om several occasions frozen the entire system when lurkjing in the sys. dlls, even thought I've told it not to do so... :/ ) 7. Might not be, "simply" add a "execution monitor thread" for each thread - let the main debugger thread handle them (thus for a single threaded app there will be two debugger threads - one for the debugger and one for the main thread). _________________ ... a professor saying: "use this proprietary software to learn computer science" is the same as English professor handing you a copy of Shakespeare and saying: "use this book to learn Shakespeare without opening the book itself. - Bradley Kuhn |
|||
27 Aug 2003, 14:07 |
|
roticv 27 Aug 2003, 15:38
Quote: Just one comment, I think that the debugger should be able to crash wothout taking donw the entire IDE, or atleast save all project files (and sak for other files to be save) - so that the risc of lossing data is minimal. Hasty I suppose? The way round it is to wrap it round seh. That would prevent the debugger to crash. You don't see ollydbg crashing right? |
|||
27 Aug 2003, 15:38 |
|
scientica 27 Aug 2003, 15:47
roticv wrote: You don't see ollydbg crashing right? I can't remember crashing it - but on several occasions it has frozen (kinda like a crash - but no error message or self termination) the system while doing something in the system dlls, even thought I've told it to skip them... _________________ ... a professor saying: "use this proprietary software to learn computer science" is the same as English professor handing you a copy of Shakespeare and saying: "use this book to learn Shakespeare without opening the book itself. - Bradley Kuhn |
|||
27 Aug 2003, 15:47 |
|
JohnFound 27 Aug 2003, 17:42
pelaillo wrote: JohnFound, Hi, pelaillo. IMO, Windows have some Debug API and all windows debugers (Olly too) uses this API to debug applications. Every program can start new process in "Debug mode" and to have full control under execution instruction by instruction. I think that Fresh must use the same API for source level Debuger, only instead of disassembling debuging application, it will use real source code. Of course, if the user prefer, there will be "CPU" window with exact machine level code - for example for tracing parts of code without source or Windows DLL's. (Delphi source level debuger work similar way.) Unfortunately I have no time to learn more about Debuging API just now, and I think it's too early to think about Debuger for Fresh, because we must wait Privalov to implement some new features of FASM - giving us tables with relations between labels and real addresses in compiled code. Without this information, it's impossible to realize source level debuger. Regards. |
|||
27 Aug 2003, 17:42 |
|
pelaillo 28 Aug 2003, 11:48
OK JohnFound,
I will wait for Privalov's work and in the meantime I will concentrate on some GDI stuff. Thanks, |
|||
28 Aug 2003, 11:48 |
|
Goto page Previous 1, 2, 3 < Last Thread | Next Thread > |
Forum Rules:
|
Copyright © 1999-2024, Tomasz Grysztar. Also on GitHub, YouTube.
Website powered by rwasa.