This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Bizarre GCC problem - how do I debug it?


>>>>> "Bruce" == Bruce Korb <bruce.korb@gmail.com> writes:

Bruce> That seems to work.  There are one or two or three bugs then.
Bruce> Either gdb needs to recognize an out of sync object code, or else
Bruce> gcc needs to produce object code that forces gdb to object in a way
Bruce> more obvious than just deciding upon the wrong file and line --
Bruce> or both.

Nothing can be done about old versions of gdb.  They are fixed.

I think the situation is better in newer versions of GDB.  We've fixed a
lot of bugs, anyway.  (I'm not sure exactly what problem you hit, so I
don't know if gdb is in fact any more future-proof in that area.)

I don't think things can ever be perfect.  GDB checks the various DWARF
version numbers, but that doesn't exclude extensions.

Bruce> I simply installed the latest openSuSE and got whatever was
Bruce> supplied.  It isn't reasonable to expect folks to go traipsing
Bruce> through upstream web sites looking for "changes.html" files ....

In a situation like this, I suggest complaining to your vendor.  We've
done a lot of work in GDB to catch up with GCC's changing output.  The
development process here is actually reasonably well synchronized.

Tom


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]