A couple of fixes
by Yann Dirson
[PATCH 1/3] Fix verbose printing of ARGS_STRING_POINTER_LENGTH
Pretty much untested, just seen when taking that piece of code as a
copypaste source.
[PATCH 2/3] Fix typos
Well, also reworded a bit
[PATCH 3/3] Avoid segfault with -v when sym is NULL in
That one happens with the following small Qt program I'm using for
tests, when run with "-v -A". Reproduced with the current debian
package.
----8<----
#include <Qt/QtCore>
#include <QtCore/QDebug>
int main(int argc, char* argv[])
{
QCoreApplication * app = new QCoreApplication(argc, argv);
qDebug() << QString("coucou");
qDebug() << app->metaObject()->className();
QDirIterator it("/tmp", QDirIterator::Subdirectories);
//while (it.hasNext()) {
// qDebug() << it.next();
//}
return 0;
}
----8<----
11 years, 10 months
- 1
- 3
latrace: plans for supporting debug symbols ?
by Yann Dirson
Hello,
latrace is currently cool for simple programs that use just libc or
some lib small enough to make (re)writing a header file reasonable. I
was looking forward to using it to investigate the interactions
between a Qt program and the Qt libs - you will understand I don't
intend to write (C-style) headers for (even a usable subset of) Qt :)
Luckily, it seems that in many cases all the necessary information is
available as debug symbols (eg. in Debian most libs, while shipped
without debug symbols, have a companion package shipping separate
debug symbols, which gcc knows how to use).
Are there any plans to access those debug symbols (through libbfd
maybe ?) in latrace ?
Best regards,
--
Yann
11 years, 10 months
- 2
- 2
- ← Newer
- 1
- Older →