check_nt problem

[Andreas Ericsson]

jeff vier wrote:
--[ snip, snip ]----
> I had my old (working) copy of check_nt backed up, so I copied it into
> place, so I'm not dead in the water or anything.
> 
> Now, here's why it's particularly curious.  I diff'd the check_nt.c from
> a known good build and it's the *exact same* as the 'bad' one!
> 
Try diffing all the files it #include's too (you might need to revert to 
older kernel headers for that), as well as the files it's linked to.
If nothing is different there, then it can only be compiler error.
Try running gdb on it. It should give you some pointers.

> Thanks for any help!
> 
> --jeff
> 
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by: IBM Linux Tutorials
> Free Linux tutorial presented by Daniel Robbins, President and CEO of
> GenToo technologies. Learn everything from fundamentals to system
> administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
> ::: Messages without supporting info will risk being sent to /dev/null
> 

-- 
Mvh / Best regards
Sourcerer / Andreas Ericsson
OP5 AB
+46 (0)733 709032
andreas.ericsson at op5.se


-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null