Re: Why doesn't this work
- From: John <jvasquez@xxxxxxx>
- Date: Mon, 07 Jul 2008 07:14:37 -0700
On Thu, 03 Jul 2008 14:29:03 -0700, Cyril Novikov
<cnovikov@xxxxxxxxxxxxxxxxxxx> wrote:
John wrote:
I don't see anything glaring. Run the preprocessor on your code andI'm sorta a newbie in lynxOS. I have done a device driver on an x86
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.
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.
thanks, I'll give that a try the first chance I get.
.
- References:
- Re: Why doesn't this work
- From: Cyril Novikov
- Re: Why doesn't this work
- From: John
- Re: Why doesn't this work
- From: zoot51
- Re: Why doesn't this work
- From: Brandon
- Re: Why doesn't this work
- From: John
- Re: Why doesn't this work
- From: Cyril Novikov
- Re: Why doesn't this work
- Prev by Date: Re: One thread wait on several condition variables?
- Next by Date: Re: Problems with interrupts on a PPC
- Previous by thread: Re: Why doesn't this work
- Next by thread: kkprint
- Index(es):
Relevant Pages
|