VisualKernel not listed as option under Project Templates

Sysprogs forums Forums VisualKernel VisualKernel not listed as option under Project Templates

This topic contains 7 replies, has 2 voices, and was last updated by  support 2 months, 3 weeks ago.

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • #21181

    andrewtheart
    Participant

    VisualKernel not listed as option under Project Templates

    After installing the latest version of VisualKernel, in Visual Studio 2017 Enterprise, VisualKernel is not listed as an available option.

     

    I was following the instructions here: https://sysprogs.com/VisualKernel/tutorials/kernel/

    #21182

    support
    Keymaster

    Hi,

    This might be caused by corrupt VS package cache. Please try following the instructions on the following page: http://visualgdb.com/support/loadfail/

    Please note that the instructions are for VisualGDB; the only difference for VisualKernel would be the package name.

    #21245

    andrewtheart
    Participant

    Sorry, that did not resolve the issue. I uninstalled one and it is still not showing up.

    It shows up correctly in Visual Studio 2015.

    #21246

    support
    Keymaster

    Hi,

    Thanks for the update. Could you please also check if the files/registry values mentioned in steps 7 and 8 are present (replace VisualGDB with VisualKernel in all names)?

    #21431

    andrewtheart
    Participant

    Yes, but it is not as much of a concern to me since I can launch it from VS 2015.

    I am getting another error when I am building the kernel.

     

    See sequence of error messages: https://imgur.com/a/lH8wX3M

     

    Error text:

     

    VisualKernel version: 3.0.2.2166
    —————— System.Exception ——————
    System.Exception: Cannot load LinuxKernelDebugHelper.ko
    at mb1.c.b(f2 b, xx1 a)
    at mb1.c.l(f2 a)
    at VisualGDB.Common_GUI.WPF.ItemizedProgressWindow.<>c__DisplayClass1_0`1.<RunAction>b__0()

     

     

    #21452

    support
    Keymaster

    Hi,

    Please try clicking the round expander button in the progress window and then check for the build error messages (or use View->Other Windows->VisualKernel Diagnostics Console).

    Most likely your kernel is missing some of the configuration options required for the optimized module handling logic.

    #21464

    andrewtheart
    Participant

    Configuring KernelDebugHelper module.
    Checking layout of ‘struct module’…
    make: Entering directory ‘/usr/src/linux-source-4.15.0/linux-source-4.15.0’
    CC [M] /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/AppendableBuffer.o
    CC [M] /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.o
    In file included from /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/AppendableBuffer.c:3:0:
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/AppendableBuffer.h:14:13: warning: ‘ResetAppendableBuffer’ defined but not used [-Wunused-function]
    static void ResetAppendableBuffer(AppendableBuffer *pBuffer)
    ^~~~~~~~~~~~~~~~~~~~~
    In file included from /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:7:0:
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/SerialInterface.h:33:26: warning: multi-character character constant [-Wmultichar]
    MODULE_LIST_SIGNATURE = ‘TSLM’,
    ^~~~~~
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/SerialInterface.h:34:27: warning: multi-character character constant [-Wmultichar]
    MODULE_EVENT_SIGNATURE = ‘TVEM’,
    ^~~~~~
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:28:2: warning: multi-character character constant [-Wmultichar]
    ‘GBDK’,
    ^~~~~~
    In file included from ./include/uapi/linux/posix_types.h:5:0,
    from ./include/uapi/linux/types.h:14,
    from ./include/linux/compiler.h:164,
    from ./include/linux/init.h:5,
    from /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:1:
    ./include/linux/stddef.h:8:14: warning: initialization makes integer from pointer without a cast [-Wint-conversion]
    #define NULL ((void *)0)
    ^
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:31:2: note: in expansion of macro ‘NULL’
    NULL,
    ^~~~
    ./include/linux/stddef.h:8:14: note: (near initialization for ‘KernelDebugDataBlock.Reserved’)
    #define NULL ((void *)0)
    ^
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:31:2: note: in expansion of macro ‘NULL’
    NULL,
    ^~~~
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper_main.c:54:13: warning: ‘make_range_writable’ defined but not used [-Wunused-function]
    static void make_range_writable(void *start, void *end)
    ^~~~~~~~~~~~~~~~~~~
    CC [M] /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/SequentialModuleInfo.o
    In file included from /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/SequentialModuleInfo.h:2:0,
    from /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/SequentialModuleInfo.c:2:
    /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/AppendableBuffer.h:14:13: warning: ‘ResetAppendableBuffer’ defined but not used [-Wunused-function]
    static void ResetAppendableBuffer(AppendableBuffer *pBuffer)
    ^~~~~~~~~~~~~~~~~~~~~
    LD [M] /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper.o
    Building modules, stage 2.
    MODPOST 1 modules
    CC /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper.mod.o
    LD [M] /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper.ko
    make: Leaving directory ‘/usr/src/linux-source-4.15.0/linux-source-4.15.0’

    insmod: ERROR: could not insert module /tmp/LinuxKernelDebugHelper-fab70f0d-4c3f-4f93-b524-7e5638fb5ccc/LinuxKernelDebugHelper.ko: Invalid module format

    #21476

    support
    Keymaster

    Hi,

    This looks like the build tools you are using are not compatible with the target system. Please try checking the ‘dmesg’ output for more details (e.g. wrong kernel version, incompatible architecture, etc). If nothing helps, please try building and loading the module manually. Once VisualKernel detects that it is loaded, it won’t try to rebuild it anymore.

Viewing 8 posts - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.