I have been working on building an ALGOL compiler for myself, buit when I try to debug the code generated by FLEX, I get SIGERRs before execution.

OK LD is deprcated? GCC -O test lex.yy.o -lc

Now the GDB works sort - of :

the code passes in my datafile, calls yylex --

Acres and Acrds of working code So I say : continue

SIGERR filenno_unlocked


I dont understand what is broken nor now to fix it.
fileno_unlocked is not suppose to generate an error.
REMEMBER this is in the code for flex. And the source has 20 lines of text.


The software is unassuming. Maybe I need to do somthing but I do not know what that might be.

Has anyone ELSE ever seen this probelm.?

gdb will produce very interesting results if you use it to debug optimised code. The reason for this is that the optimiser reshuffles your code, removes bits of it, inlines loops and various other issues. So the binary code doesn't map exactly onto its source code; gdb just follows the binary.

Take out the -O, and try using -g instead (which adds symbol information to the executable). You should then be able to debug much more easily.

If fileno_unlocked is generating an error, then the most likely explanation is that fileno_unlocked is being used incorrectly, contains a bug, or uses something else that contains a bug.

Hope that helps,

—Robert J. Lee

The thought was good but I am not runing an optimizing compile/ I am linking with gcc -o test lex.yy.o -lc

This should be a good command line to link a compiled unit. to compile it gcc - g -c lex.yy.c

Then go get SIGERR fileno_unlocked

this is not a proper error. I do not understand what is happening and I need to to know how to fix it.

I am building a compiler. the first step is to build a tokenizer.... I cant even get it to process enough to fix the logic falults. ; It is clear that large projects compile and execute nicely.

So I am doing something wrong or leaving something out.