Some headers(errno.h etc) are not sync to local for openSUSE linux, strange !

Sysprogs forums Forums VisualGDB Some headers(errno.h etc) are not sync to local for openSUSE linux, strange !

This topic contains 4 replies, has 2 voices, and was last updated by  Jimm Chen 3 months, 2 weeks ago.

Viewing 5 posts - 1 through 5 (of 5 total)
  • Author
    Posts
  • #13335

    Jimm Chen
    Participant

    I’m trying VisualGDB 5.3 r8, and have confirmed a problem for openSUSE(13.1 and 43.1, 43.2).

    Using openSUSE and target machine, quit some header files within the asm directory, like errno.h, fcntl.h, are not automatically copied to RemoteSourceCache folder. But with Ubuntu 14.04, no such problem.

    Could you please check into this problem and get it fixed?

    #13337

    support
    Keymaster

    Hi,

    Different Linux distros may have slightly different include directory layouts, so please double-check that the files actually exist in the same directory on the other machine (please also double-check that you are looking at a correct folder on the Windows side – the dir.txt file should contain the remote directory name).

    If you can confirm this, please try reloading all include directories via VisualGDB Project Properties. If this doesn’t resolve the problem either, please check that you can access the header files from your current user account (incorrectly set permissions would prevent VisualGDB from synchronizing those files properly).

    #13338

    Jimm Chen
    Participant

    Sure they actually exist.

    • F7 compile and link ok. The compiler and linker is run from the very target openSUSE.
    • If I manually copy errno.h and fcntl.h from openSUSE to the local corresponding subdirectory, then click “Search the same directories again”, then VisualGDB no longer complains.

    So please install an openSUSE VM and verify it yourself.

    #13339

    support
    Keymaster

    Hi,

    Thanks, looks like VisualGDB was handling a certain type of hard links in tar archives incorrectly. We have fixed it in the following build: http://sysprogs.com/files/tmp/VisualGDB-5.3.18.1978.msi

    Please note that you would need to reload the IntelliSense directories via VisualGDB Project Properties.

     

    #13378

    Jimm Chen
    Participant

    Great to see it fixed, verified. Hope to see a formal release soon.

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

You must be logged in to reply to this topic.