RE: [line-devel] RE: [line] Applications list broken

[Andrew G. T. <ta...@ib...>]

> -----Original Message-----
> From: lin...@li...
> [mailto:lin...@li...]On Behalf Of Michael Vines
> Sent: Thursday, June 07, 2001 1:32 AM
> To: Andrew G. Tereschenko
> Cc: lin...@li...
> Subject: [line-devel] RE: [line] Applications list broken
>
> Actually I originally started writing LINE in MSVC because the integrated
> debugger is so much nicer to use than gdb.  However once I started using
> the Cygwin DLL, I switched over to gcc.  Most of the code should be
> portable between the two compilers.  A couple problem points would be:
>
> - gcc specific inline assembly in src/linexec/asm.h
>   (but it is no big deal to put a compiler specific #ifdef around it)

I have a few words about assembly and current interupt handling routing
install.

Here is a quote from DDK :
http://www.osr.com/ddk/intrupts_87qf.htm
"To register an ISR, a driver's DispatchPnP routine must call
IoConnectInterrupt
 when it receives an IRP_MN_START_DEVICE request. In response, the I/O
Manager creates an interrupt object for each processor that the device can
interrupt."

Are you shore that your IDT modification code will work under SMP ???

I have a proposal to fix your code by using sample from :
http://www.wdj.com/articles/2000/0002/0002a/0002al2.htm
Full article:
http://www.wdj.com/articles/2000/0002/0002a/0002a.htm

If we will port asm - i would like to make it as inline asm in C function.

> - gcc preprocessor extensions in src/common/log.h
Not a problem if we redefine log functions/param order.

> But the biggest problem is that LINE needs the Cygwin runtime environment.
Do we realy need full Cygwin implementation ??? I expect that LINE will
map syscalls directly to Win32, without using Cygwin.
I don't wanna mix bugs/implementation restrictions from Cygwin in Line.
But i understand that it need additinal time to move mapping code from
Cygwin
source base to Line.

> From what I've read on the Cygwin site you can't mix the Cygwin runtime
> with the MSVC runtime.  This means at the very least you need to link LINE
> with the Cygwin/gcc linker.  It may be possible to compile the object
> files using MSVC, but I don't see much point to it (other than that MSVC
> does compile much faster than gcc on my machine).

Hmm. I can agree that this _is_ a problem. There was one probosal in 1998
to add init code in DLL but nothing was done. I will make some research.
This issue can push us to non-Cygwin implementation.
Are you agree if there will no Cygwin dll usage ?

> What would be really cool is if the gdb debugging information in the
> resulting executables could be massaged into a format recognizable by
> MSVC.

No one want follow standarts.  Even OpenSource developers create own
standarts :o(

=============================
Andrew G. Tereschenko
Software Engineer
Integrated Banking Information Systems
ta...@ib...