Tristan Van Berkom <tvb <at> gnome.org> writes: > > On Tue, 2007-05-22 at 20:29 +0000, Jeremy Roberson wrote: > [...] > > And I get a segmentation fault. I then tried ldd and gdb and I get an instant > > segmentation fault. If I unset the LD_LIBRARY_PATH variable and then try ldd > > and gdb, they work but the application fails because it's linking against older > > libraries. > > > > Any ideas would be greatly appreciated. > > I'm not sure off hand whats going wrong in your app, > you might try a true jailed environment using a chroot, etc - > or at least run a short study on existing jail environments > and what details they attend to to make sure apps/compilation > works properly. > (sounds to me like you are not even reaching main() from your gcc > start stubs, maybe you have something set to preload on the target > system ? I dont know...) > > Cheers, > -Tristan >
Okay, I tried on two of my target systems and I'm noticing a pattern. When I attempt to run the application without setting the LD_LIBRARY_PATH, the application fail due to library incompatibilities which, is expected. As soon as I set LD_LIBRARY_PATH variable, every command executed in the shell fails with a segmentation fault. Something about the LD_LIBRARY_PATH environment variable is causing problems. Based on my reading, the dynamic linker checks LD_LIBRARY_PATH first and then continues checking the linker cache so, setting this variable shouldn't in my opinion cause all commands executed in the shell to fail. In case your curios, the two distributions I'm testing on are GuadaLinex and LinKat. We're targeting a ton more but, I'm working with these two until I can figure out how to get it to work on them Thanks, Jeremy _______________________________________________ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list
