Why doesn't this work

John

unread,

Jun 30, 2008, 3:47:41 PM6/30/08

to

I am doing a device driver in LynxOS 4.0.
The following is used in all of our device drivers include one for
lynxOS x86. this code was cloned from the x86 for the development of a
device driver for ppc.

#ifdef DEBUG
#define DEBUG_PRINT(level, format, a...) \
if ((level) & debug_print)kkprintf(format, ## a)
#else
#define DEBUG_PRINT(level, format, a...)
#endif

DEBUG is defined
debug_print was initialize to a -1 and level is passed to the
DEBUG_PRINT macro.

In the actual device driver, there might be something like this

DEBUG_PRINT(DEBUG_INIT,"this is a debug statement %x\n",error_msg);

where DEBUG_INIT might be set to #define DEBUG_INIT 1.

All other driver it works. I'm just having problems with lynxOS
compiling for a ppc development driver.

if I do kkprint() in the driver code, I get a printout.

Any Ideas?

Cyril Novikov

unread,

Jul 1, 2008, 5:44:07 PM7/1/08

to

Hardly. I've scanned your post for any concrete problem symptoms, and found only
this: "I'm just having problems with lynxOS compiling for a ppc development
driver." Well, that's unfortunate. But until you explain what your problem is
exactly (quote error message, code, etc), you'll have trouble finding helpful Ideas.

John

unread,

Jul 2, 2008, 2:05:42 PM7/2/08

to

Well, I'm not having any problems compiling. No error message. I just
can't get the DEBUG_PRINT macro above to work. I only get debug print
statements to work when I eliminate the,"if (level & debug_print)"

zoot51

unread,

Jul 2, 2008, 5:18:08 PM7/2/08

to

maybe the compiler has decided that debug_print returns 0 or void and
therefore optomised it out.

Brandon

unread,

Jul 2, 2008, 8:11:38 PM7/2/08

to

I don't see anything glaring. Run the preprocessor on your code and
print the listing. That will tell you what is actually going to the
compiler. Write up a test case, and then post the results of the
processed listing if you can't see the problem. Since DEBUG_PRINT is a
macro we need the pre-processed code to help.

John

unread,

Jul 3, 2008, 10:58:45 AM7/3/08

to

On Wed, 2 Jul 2008 17:11:38 -0700 (PDT), Brandon <sgar...@gmail.com>
wrote:

I'm sorta a newbie in lynxOS. I have done a device driver on an x86
platform (many many moons ago) using basically the same code.
DEBUG_PRINT macro works find.
Anyway, how do a run the preprocessor on my code. Or is there a way to
generate a compile listing where I can take a look at the generated
code.

I'm a Windows Device Driver guy. Please don't hold that against me.

John

Cyril Novikov

unread,

Jul 3, 2008, 5:29:03 PM7/3/08

to

John wrote:

>> I don't see anything glaring. Run the preprocessor on your code and
>> print the listing. That will tell you what is actually going to the
>> compiler. Write up a test case, and then post the results of the
>> processed listing if you can't see the problem. Since DEBUG_PRINT is a
>> macro we need the pre-processed code to help.
> I'm sorta a newbie in lynxOS. I have done a device driver on an x86
> platform (many many moons ago) using basically the same code.
> DEBUG_PRINT macro works find.
> Anyway, how do a run the preprocessor on my code. Or is there a way to
> generate a compile listing where I can take a look at the generated
> code.

Copy/paste the compile command that gets executed when you run make to the
command prompt. But instead of the -c option, pass -E to gcc. The output file
(specified after -o) will contain preprocessed code.

John

unread,

Jul 7, 2008, 10:14:37 AM7/7/08

to

thanks, I'll give that a try the first chance I get.