| Subject: | Re: Problem migrating to EM64T |
|---|---|
| From: | Paul Pluzhnikov <ppluzhnikov-nsp@xxxxxxxxx> |
| Date: | Wed, 16 Jul 2008 19:52:27 -0700 |
| Newsgroups: | gnu.gcc.help |
emilbarton <bartonemil@xxxxxxxxx> writes: > I've changed my cpu for an EM64T (core 2) and installed a new Linux > system, but now after having recompiled my code I obtain lots of > output like : > "14689: symbol=fprintf; lookup in file=./myprogram [0]" > at the end of the normal output of my program (when it does not simply > end with a segfault). This message comes from dynamic loader when debugging is turned on. You can see this for yourself doing: env LD_DEBUG=symbols /bin/date The fact that you are getting these messages without LD_DEBUG means that you have a bug in your program, which corrupts dynamic loader into believing that debugging is turned on. The bug likely exists in 32-bit version as well, but you corrupt something else, and so do not observe the result of corruption. You may wish to test your program with Valgrind, Purify or Insure++ and fix all bugs that they report. Cheers, -- In order to understand recursion you must first understand recursion. Remove /-nsp/ for email. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | How do I get a warning or error when returning values from functions returning void in GCC?, bgutter |
|---|---|
| Next by Date: | Re: what does the "branch" mean in the gcov command?, asobou . tama |
| Previous by Thread: | Problem migrating to EM64T, emilbarton |
| Next by Thread: | How do I get a warning or error when returning values from functions returning void in GCC?, bgutter |
| Indexes: | [Date] [Thread] [Top] [All Lists] |