[Development] QInotifyFileSystemWatcherEngine might have incomplete data?

Mark Gaiser markg85 at gmail.com
Sun Nov 17 21:23:27 CET 2013

On Sun, Nov 17, 2013 at 9:20 PM, Mark Gaiser <markg85 at gmail.com> wrote:
> On Sun, Nov 17, 2013 at 8:03 PM, Olivier Goffart <olivier at woboq.com> wrote:
>> On Sunday 17 November 2013 19:07:48 Mark Gaiser wrote:
>>> 4. GDB (or whatever you used) should hit the bearkpoint. Now inspace
>>> the "event" members (name specifically). It's empty while it shouldn't
>>> be.
>> Hi,
>> I'd add a qDebug()  to be sure.
>> Maybe it's just GDB giving wronf information.  Perhaps the data as been
>> optimized.  Perhaps gdb think the name has lengh 0 because it is declared as a
>> char[].
> Hi Oliver,
> I tried your suggestion and that indeed works though not as i would expect it.
> Yes, it does get printed on screen when i put event.name in a qDebug line.
> However, none of the emit signals in that function (readFromInotify)
> work anymore when i use "event.name" there. Anywhere! I just tried
> that out since you've had send the reply.
> You can find the diff of the stuff that's i've done thus far. Just
> adding this to your code breaks all the emits and i have no clue as to
> why that happens or how it's even possible.
> If you have any clue.. please do tell.

Sorry, forgot the diff: http://pastebin.kde.org/pzqb2jph6
Lifetime of 30 days.

More information about the Development mailing list