RE: [line-devel] RE: Interrupt vector

[Michael V. <mi...@bl...>]

On Wed, 13 Jun 2001, Andrew G. Tereschenko wrote:

> ntddk.h:119
> extern NTSYSAPI CCHAR KeNumberProcessors;
> ntdef.h:504
> typedef char CCHAR;          // winnt
>
> I think it's my DDK incompatibility.

I can't seem to find any version information on the DDK that I have, but
just downloaded it from Microsoft about a month ago.  In my DDK, it's:

wdm.h:111
extern PCCHAR KeNumberProcessors


> I will not post files (even 8K in ZIP) in list, here is a link:
> http://tag.odessa.ua/line/20010613.zip

ok, sounds good.


> > > Note about 64K pages - we heed own pagefault handler to support
> > SEG_FAULT
> > > signal ?
> >
> > I'm not sure what you mean?
>
> Can linux app proccess SEG_FAULT signal ?

Good question.  I wrote a quick little Linux app:

-------
#include <signal.h>
#include <stdio.h>

void seg_fault(int x)
{
  printf("Opps, segfault occured.\n");
  exit();
}

int main()
{
  signal(SIGSEGV, seg_fault);

  printf("Trying a segfault.\n");
  *(char*)0 = 0;

  return 0;
}
-----

Under Linux, the output is:
-----
$ ./fault
Trying a segfault.
Opps, segfault occured.
$
-----

When running under LINE without the driver enabled, the LINE debugger
kills the application when the segfault occurs.  LINE really should try to
pass that back to the app.  This will be a little tricky to do, but it's
possible.

With the driver, the app output "Trying a segfault" and then it just sits
there doing nothing!



I just found a new BSOD :)

I reboot my system with the driver installed (the driver is set for ..),
then I immediately remove the driver with 'remove.bat'.   That gives a
"BAD_POOL_CALLER" BSOD.

However if I reboot, run LINE once, and then remove the driver I don't get
a BSOD.



Mike