drjonem

Forum Replies Created

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • in reply to: VisualGDB crashing VS2022 on one PC. #34705
    drjonem
    Participant

    Thanks, will give it a go.

    in reply to: VisualGDB crashing VS2022 on one PC. #34695
    drjonem
    Participant

    Hi,

    Sorry for the delay responding, holidays got in the way!

    I am using 6.0 Beta 1.

    I have obtained a stack trace, (see below). Also, when having the debugger attached, it reported this exception:

    System.AccessViolationException: ‘Attempted to read or write protected memory. This is often an indication that other memory is corrupt.’

    Stack trace:

    [Managed to Native Transition]
    > Microsoft.VisualStudio.Package.LanguageService.15.0.dll!Microsoft.VisualStudio.Package.LanguageService.RefreshUI() Line 924 C#
    Microsoft.VisualStudio.Package.LanguageService.15.0.dll!Microsoft.VisualStudio.Package.LanguageService.OnParseComplete(Microsoft.VisualStudio.Package.ParseRequest req) Line 919 C#
    VisualGDBPackage2022.dll!a43.l2(Microsoft.VisualStudio.Package.ParseRequest a) Unknown
    WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) Unknown
    WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source, System.Delegate callback, object args, int numArgs, System.Delegate catchHandler) Unknown
    WindowsBase.dll!System.Windows.Threading.DispatcherOperation.InvokeImpl() Unknown
    WindowsBase.dll!MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(object obj) Unknown
    mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) Unknown
    mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx) Unknown
    mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown
    WindowsBase.dll!MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext executionContext, System.Threading.ContextCallback callback, object state) Unknown
    WindowsBase.dll!System.Windows.Threading.DispatcherOperation.Invoke() Unknown
    WindowsBase.dll!System.Windows.Threading.Dispatcher.ProcessQueue() Unknown
    WindowsBase.dll!System.Windows.Threading.Dispatcher.WndProcHook(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) Unknown
    WindowsBase.dll!MS.Win32.HwndWrapper.WndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam, ref bool handled) Unknown
    WindowsBase.dll!MS.Win32.HwndSubclass.DispatcherCallbackOperation(object o) Unknown
    WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate callback, object args, int numArgs) Unknown
    WindowsBase.dll!System.Windows.Threading.ExceptionWrapper.TryCatchWhen(object source, System.Delegate callback, object args, int numArgs, System.Delegate catchHandler) Unknown
    WindowsBase.dll!System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority priority, System.TimeSpan timeout, System.Delegate method, object args, int numArgs) Unknown
    WindowsBase.dll!MS.Win32.HwndSubclass.SubclassWndProc(System.IntPtr hwnd, int msg, System.IntPtr wParam, System.IntPtr lParam) Unknown
    • This reply was modified 1 year, 2 months ago by support. Reason: formatting
    in reply to: Problem with BSP_ALIAS #34063
    drjonem
    Participant

    Hi,

    Thank you for the prompt fix!

    Apologies for not updating re the flags – they were set in the BSP depending on memory destiation used and I hadn’t realised that, so that was my problem.

    Thanks again,

    Jon.

    in reply to: Problem with BSP_ALIAS #34057
    drjonem
    Participant

    Hi,

    I’m still not having any luck with this. As suggested, I tried creating a very simple STM32 project – see attached CMakeLists.txt.

    There seems to be a problem with cmake_parse_arguments in bsp_compile_definitions. The arguments are passed correctly; however, if the arguments are BSP_ALIAS BOOT_BSP, BSP_ALIAS is not found. If the arguments are ALIAS BOOT_BSP then somehow BSP_ALIAS is found and parse as BOOT_BSP.

    I think I will revert to using two solutions but if you can find a solution to the above, I would be interested to know as it seems very odd behaviour.

    Thanks,

    Jon

    Attachments:
    You must be logged in to view attached files.
    in reply to: Can't connect to yocto toolchain on WSL2_Win11 #31898
    drjonem
    Participant

    Hi,

    I investigated Windows Firewall more closely – for some reason there were two rules for Visual Studio. I deleted one of them and now it is all working fine (and really well!).

    The only odd thing is why turning Windows Firewall off didn’t help; maybe a Win 11 bug?

    All I need to do now is create a separate platform for local (wsl) builds and remote builds and I will have a very flexible system.

    Thanks for your help.

     

    Jon.

    in reply to: Package Revision History #29551
    drjonem
    Participant

    Thank you, that’s very helpful. I must admit, I’d looked through the VisualGDB revision history but hadn’t spotted that the maintenance information was at the end of the list. I blame my old eyes! 🙂

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