Hello, after going through the Peek & Poke serie, the documentation and gdbmacros.py, yesterday, for a few hours, i tried to have the debugger display sensible information about, say, __m128i; the only appreciable result being an elevated blood pressure.
Now that i can express myself without expletives every other word, a few bullet points: . user made dumpers are simply not working in 2.1.0 beta1 (2.0.92, x86-64 linux). . but they do back in, ie, 2.0.1 (revision 97d831e3de). . there's no way tell what's going on, going through pages after pages of cryptic log is an exercise in futility. . even armed with a possibly working custom dumper, "native" types are ignored; can't overload them. . and if you wrap such type (and defeat the purpose), pick it out, then, you're left wondering how one's supposed to manipulate them; implementations for other types provide no clue. To sum it up, the default display for packed scalars is severely lacking: __m128 and __m128i are in fact aliasing a whole family of types and while gdb knows about, you can't cast to, say, __v16qi on the fly in qt creator's debugger. A custom dumper is required, but as far as know, it's not even possible. Help. PS: who thought displaying __m128i as 2 signed 64bit integers by default was a good idea? :) PPS: the register view is slightly better, but of no use in debug builds. _______________________________________________ Qt-creator mailing list Qt-creator@trolltech.com http://lists.trolltech.com/mailman/listinfo/qt-creator
