Hi Francesco, interesting stuff, I've never heard about build-id before :) Anyhow, it's not something that you can query at runtime, right? I tend to agree with Oliver, just choosing an arbitrary number might be the simplest and most straightforward method ...
Regards Kai ________________________________________ From: [email protected] [[email protected]] on behalf of ext Francesco R.(vivo) [[email protected]] Sent: Thursday, January 26, 2012 12:23 AM To: [email protected] Cc: Thiago Macieira Subject: Re: [Development] Work on qDebug and friends - debug areas On Wednesday 25 January 2012 20:07:57 Thiago Macieira wrote: > On Wednesday, 25 de January de 2012 18.28.18, Olivier Goffart wrote: > > KDebug::registerArea needs a registery. That works for KDE, but I don't > > know if that is a good idea for Qt don't know if it can be applied to all platform or even linux, but both binutils linkers (bfd and gold) support --build-id, which is already used by distributions. it can be generally read from an elf file like this: readelf -x .note.gnu.build-id /lib/modules/3.2.1/misc/vboxnetflt.ko \ | awk '$NF ~ /GNU/ { getline; printf $2$3$4$5; getline; print $2 }' it require "--build-id" flag passed to the linker, or it can be computed by `debugedit` as extracted by the rpm tool. the id would change even for the same object with whatever change of compilation tools or settings and it would not work under other OS, so I'm not suggesting this, just bringing it to your attention. > TBH, I really don't want the default debugging system in Qt to rely on > config files. We're removing QSettings dependency from QtCore, so there's > nothing to use. +1 $ wc -l ~/.kde4/share/config/kdebugrc 2837 .kde4/share/config/kdebugrc > A third-party plugin can have a configuration mechanism to use the areas > that qDebug defines. _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development _______________________________________________ Development mailing list [email protected] http://lists.qt-project.org/mailman/listinfo/development
