hello mike,
> Hi Tony,
>
> Hmmm, another intermittent SIGSEGV. That is the second report.
>
> Is there anyone out there who can reproduce this on demand and
> is willing and able to help me get a stack trace?
>
> I do have one idea about this. Could you please try this program
> on your machine:
>
> #include <stdio.h>
>
> int main( int argc, const char * argv [] )
> {
> printf( "%s\n", (char *) 0 );
> return 0;
> }
>
> Be sure to compile it with "-O2 -fomit-frame-pointer".
>
> tkparse likes to printf through a null pointer occasionally. If you
> see "(null)" on your output, you have a printf that doesn't fall over.
> If you get a segmentation fault, that would explain why your tkparse
> is seg-faulting.
>
> But it could be something else entirely.
>
> Michael Elizabeth Chastain
> <mailto:mec@shout.net>
> "love without fear"
i tried that and the result was:
[root@m1 ~/test]# ./test
(null)
compiled using:
gcc -O2 -fomit-frame-pointer -o test test.c
peter hanecak
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/