Page 1 of 1
Howto find out what prevents programs from working?
Posted: Mon Feb 14, 2005 11:12 pm
I would be interrested on working on ReactOS application compatiblility, and therefor it would be good to know howto get informations what prevents programs from working under reactos.
Wine prints out "fixme"s or "unimplemented" messages, however under ReactOS apps simply quit btw. crash withouth any useful debug messages.
So, whats the best way to find out whats going wrong?
Thanks in advance, lg Clemens
Posted: Tue Feb 15, 2005 12:07 am
you must compile reactos with DBG 1 und optimized 0 then you become the debug informations (im not surbe but i mean the default is the serial port as device for the debug informations) lokk in the wiki to find out more!
Posted: Tue Feb 15, 2005 12:24 am
was not able to find anything
Posted: Tue Feb 15, 2005 11:36 am
nice would be some application which runs natively in ROS and shows always the latest API call which was made by a native application....
so one like me could see which one most propably caused the error....
does someone know such an application?
That would be great!
Posted: Tue Feb 15, 2005 2:42 pm
Well that would be great.
But it also means that we would need to write pass-through-libararies for all our libs, as far as I know, since in memory application and dll are one thing, right?
Re: That would be great!
Posted: Tue Feb 15, 2005 2:51 pm
Posted: Tue Feb 15, 2005 3:39 pm
i rust read the short description, didn't look up anything else.... but maybe this might be helpful?!!
Posted: Tue Feb 15, 2005 4:18 pm
Well, its for Linux and just a syscall displayer. Between syscalls and API-calls there is a big difference and I am in doubt its possible to trace from syscalls back to the missing API-functions.
Maybe there should be included big todo/unimplemented/fixme function dummies?
@blight: Well, do you have an idea how this could be handled?
Posted: Wed Feb 16, 2005 5:51 am
Matt Pietrek's excellent book: "Windows 95 System Programming Secrets" contains the source code of an API interception utility called APISpy32. This utility was initially published as part of an article written by Matt for the Dec 1995 issue of MSJ. A newer version of APISpy32 is available and can be DOWNLOADED at Matt's web site at http://www.wheaty.net
. not sure if that helps?
Posted: Wed Feb 16, 2005 4:25 pm
Posted: Thu Feb 17, 2005 11:10 am
Just start with a simple existing driver (drivers/dd/null comes to mind) and take it from there.