-----BEGIN PGP SIGNED MESSAGE-----
~ Ok, thanks for the explanation.
I'm just surprized and disappointed that no error message was displayed, either durring the compile or the dlopen load.
Why does the programmer have to remember every system function name and avoid them?
Jay
Andrew Pinski wrote: | | On Apr 14, 2005, at 10:32 PM, Jay Summet wrote: | |> -----BEGIN PGP SIGNED MESSAGE----- |> |> I ran into an interesting bug when attempting to add imlib2 to a |> program that |> uses GLUT. The program would compile/link fine, but segfault when the |> imlib_load_image() call was made. (initial call to imlib) |> |> The fix? |> |> change: |> int time; |> |> to: |> //int time; |> | | time is a standard C function so if you declare a variable, well you just | overwrote it, this is not a GCC bug or even a imLib2/glut bug but | a bug in your program. | | -- Pinski | -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (SunOS) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBQl/HKrWkkhmZq4xxAQHOEgP9Gy5gMquKNCk1BYmMumbKjIYIW5X2/h6l EWnE5ER27VwwNL6WK8rGLmx4rsx4s6u3VeCl2Ezk44+YbQP0JahxJ1tA5/ENmHDe VWDsqNVciD0gzbCMPk+FLar/fg6rQXn5wsu1QutxkMNwPvrC8LMYkVIp+X8rwNje axL+nSsR1NY= =5peu -----END PGP SIGNATURE-----
