Barry Smith <[EMAIL PROTECTED]> writes: > I had an experience similar to Emil's on my Apple G3 Powerbook. When I > compiled gtimer on my box, with or without debugging symbols, the > program worked.
Did you build the Debian package itself, or did you download the upstream source and build that? I don't have access to a Debian PowerPC system, which has hurt my ability to investigate this. I can change the package to not use optimization on PowerPC if that fixes the problem, but I'd like to be able to verify it first. And if a simple rebuild fixes the problem, that's even better (although there have been no apparently-relevant changes to gcc). > I'm not very familiar with gdb (though I want to be). If I compile from > source with debugging symbols, and then run the binary installed in etch > with apt-get (which crashes), and then run that core against my own > compiled binary, is that what is needed? What I don't understand is > whether or not a binary compiled at some other time, that dumps core, > can then be examined with gdb using a binary compiled later. No, you have to use gdb with the same binary, I'm afraid. Otherwise, the resulits are meaningless. -- Russ Allbery ([EMAIL PROTECTED]) <http://www.eyrie.org/~eagle/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
