my app started spewing odd output



  • ...as usual, I don't know what I did to cause this. This app has been working without this behavior for several days. A couple of hours ago, I began to get this output:

    *******A..........Anikash*********
    *******B..........Anikash*********
    [what follow is displayed after my widget.show() call]
    Window Class Name - [Qt5QWindowIcon]
    Hook() - HCBT_CREATEWND child/popup window
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******Activated..........Anikash*********
     HCBT_SETFOCUS Before
     HCBT_SETFOCUS Before
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******A..........Anikash*********
    *******B..........Anikash*********
    *******Activated..........Anikash*********
     HCBT_SETFOCUS Before
     HCBT_SETFOCUS Before
    

    I've deleted the build directory, done a clean and a qmake, and I'm getting the same results.
    Any idea what I did to cause this? And who is Anikash?

    Thanks...


  • Lifetime Qt Champion

    Hi,

    Got any update / new software on your machine ?



  • Well, given that I'm running Windows 10, that's always a possibility.

    Seriously, nothing new from Qt. The app is fairly self contained, too...no third-party libraries or anything that wasn't there yesterday.


  • Qt Champions 2016

    @mzimmers
    Hi
    where do you see "A..........Anikash**"
    is that compiler warnings or stack trace or what is it ?



  • runtime output. Shows up in the Application Output window of Creator. Does so whether or not I run the debugger.

    EDIT: I also get it when I run a release build.


  • Qt Champions 2016

    @mzimmers

    *******A..........Anikash*********
    

    completely like that ? it looks like gibberish.



  • Yes, exactly as I've entered it here.

    Anikash is a name; I figured maybe someone who helped build Qt put his name somewhere in an output statement in the event something weird occurred.

    I love problems like this.


  • Qt Champions 2016

    @mzimmers
    Grepping source of Qt 5.9 for Anikash
    So far no hits.



  • Contents of my project file:

    #-------------------------------------------------
    #
    # Project created by QtCreator 2017-09-08T14:17:25
    #
    #-------------------------------------------------
    
    QT       += core gui serialport
    
    greaterThan(QT_MAJOR_VERSION, 4): QT += widgets
    
    TARGET = [removed by mzimmers for posting to Qt forum]
    TEMPLATE = app
    
    # The following define makes your compiler emit warnings if you use
    # any feature of Qt which has been marked as deprecated (the exact warnings
    # depend on your compiler). Please consult the documentation of the
    # deprecated API in order to know how to port your code away from it.
    DEFINES += QT_DEPRECATED_WARNINGS
    
    # You can also make your code fail to compile if you use deprecated APIs.
    # In order to do so, uncomment the following line.
    # You can also select to disable deprecated APIs only up to a certain version of Qt.
    #DEFINES += QT_DISABLE_DEPRECATED_BEFORE=0x060000    # disables all the APIs deprecated before Qt 6.0.0
    
    
    SOURCES += \
        main.cpp \
        widget.cpp \
        serial.cpp \
        aes.cpp \
        file.cpp \
        xmlparser.cpp \
        encryption.cpp \
        authentication.cpp \
        tlsdata.cpp
    
    HEADERS += \
        widget.h \
        serial.h \
        aes.h \
        file.h \
        xmlparser.h \
        encryption.h \
        authentication.h \
        tlsdata.h
    
    FORMS += \
    		widget.ui
    
    

  • Moderators

    @mzimmers Run this on your project directory:

    grep -rins "anikash"

    and see if there are any results. That is either coming from your code or once I saw someone replaced the machine compiler to mess without another coder. The compiler did similar stuff. That would be a lot of effort to go through to mess with someone imo but it happens.


  • Moderators

    HCBT_SETFOCUS is a parameter received from a callback to SetWindowsHookEx(). Basically it's a system wide hook to app events, which means something on your system registered it. It's not necessarily your app or anything related to Qt. If it's not your app it can be anything from a driver, some utility app to some malware.
    As to who Anikash is - probably someone who wrote the thing. Why is he hooking to other applications events? - good question.



  • Chris - your message reminded me that I'd downloaded an LG utility (On Screen Control) just before this problem started. I deleted it, rebooted, and...no more spewage.

    Wow...just wow.

    Thanks to all who played...


  • Moderators

    Aww... no fun :) I was going to suggest to write your own debug hook to sniff who's sniffing you, but oh well. I'm glad I could help ;)


  • Qt Champions 2016

    @Chris-Kawa
    Haha i was about to ask you if it was possible to enumerate which process installed the
    hook. Snif the sniffer sounds like fun ;)



  • Yeah, thanks again...it's worth pointing out that this utility came straight from LG's support web page. I wonder how the execs there would feel about someone putting smartass-ware out there on the web for all to find...


  • Moderators

    @mzimmers
    I doubt any exec would be bothered. I don't want to sound prejudiced or anything but I've worked for a large, heartless corporation like LG once and so called "low cost production sites" (often meaning equally low quality) of such companies are almost exclusively located in the part of the world where Anikash is a pretty popular name. I mean people would be scared to use any electronics if they knew the quality of some of that code...
    I guess it's like knowing we're all living on a melted lava core rock, speeding through frozen void and shielded from deadly radiation by a paper thin shroud of gas. Some stuff you just have to suppress and learn to live with or you'd go insane :)


Log in to reply
 

Looks like your connection to Qt Forum was lost, please wait while we try to reconnect.