Howto find out what prevents programs from working?

All development related issues welcome

Moderator: Moderator Team

Post Reply
Linuxhippy
Posts: 39
Joined: Fri Dec 03, 2004 2:24 pm

Howto find out what prevents programs from working?

Post by Linuxhippy » Mon Feb 14, 2005 11:12 pm

Hello!

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

Pentiumforever
Posts: 198
Joined: Sun Jan 16, 2005 5:47 pm
Location: Duesseldorf, Germany
Contact:

Post by Pentiumforever » 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!

Linuxhippy
Posts: 39
Joined: Fri Dec 03, 2004 2:24 pm

Hmm...

Post by Linuxhippy » Tue Feb 15, 2005 12:24 am

was not able to find anything :-(

loki1985
Posts: 82
Joined: Tue Dec 07, 2004 1:39 pm

Post by loki1985 » 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?

Linuxhippy
Posts: 39
Joined: Fri Dec 03, 2004 2:24 pm

That would be great!

Post by Linuxhippy » 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?

blight
Developer
Posts: 35
Joined: Tue Nov 30, 2004 10:34 pm
Location: away

Re: That would be great!

Post by blight » Tue Feb 15, 2005 2:51 pm

;;;
Last edited by blight on Wed Feb 23, 2005 1:50 pm, edited 1 time in total.

loki1985
Posts: 82
Joined: Tue Dec 07, 2004 1:39 pm

Post by loki1985 » Tue Feb 15, 2005 3:39 pm

http://sourceforge.net/projects/strace/

i rust read the short description, didn't look up anything else.... but maybe this might be helpful?!!

Linuxhippy
Posts: 39
Joined: Fri Dec 03, 2004 2:24 pm

Hmm :-(

Post by Linuxhippy » 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?

lg Clemens

@blight: Well, do you have an idea how this could be handled?

Viator
Posts: 90
Joined: Wed Feb 16, 2005 3:53 am

Post by Viator » 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?

blight
Developer
Posts: 35
Joined: Tue Nov 30, 2004 10:34 pm
Location: away

Post by blight » Wed Feb 16, 2005 4:25 pm

Last edited by blight on Wed Feb 23, 2005 1:50 pm, edited 1 time in total.

GvG
Posts: 499
Joined: Mon Nov 22, 2004 10:50 pm
Location: The Netherlands

Post by GvG » 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.

Post Reply

Who is online

Users browsing this forum: No registered users and 8 guests