Search:

I'll try those debugging tools. I usually just used the high tech printf debugger approach (I'm sure you guys know the kind of errors that causes!) until my professor showed me gdb (he couldn't find...

these are all my memory allocs with the exception of add_cmd which just does a strdup on the parameter that is passed to it.

why would allocating an extra node cause a seg fault? should I...

yeah I did have it allocated as:


size = sizeof(opNode) + ((nops - 1) * sizeof(nodeType*));


but that seg faulted even on the 64. :(

this might be impossible to debug if you can't see...

I checked and rechecked and rechecked. . .to make sure I'm passing the correct number of arguments, so pretty darn sure that is not the problem. In the opr() function the ptr->op.oprs[i] are of...

here is some of the more relevant code. It makes a parse tree in memory (each node is a operator that points to it's operands). ex() is called when the parse tree has been completely created.
...

did try debugging with gdb
found where. just can't figure out why. :( just the .y file is 490 lines so not good to post. Why would it run under 64 if the program is overrunning memory?

all my allocs either use sizeof() or I just do a strdup

Hi! I have a program (created a simple compiler using lex and yacc). I compile and run the program on my 64(SUSE) and it runs fine -- also worked for someone else on 64(Gentoo), but when I compiled...