- This topic has 2 replies, 3 voices, and was last updated 10 years, 1 month ago by
.
-
Posts
-
Hi,
I use Slackware 14.1 with custom build kernel 3.10.17.
and have errors while i import kernel symbols after kernel rebuild.
Visual Studio menu => TOOLS -> Linux Kernel Symbol Manager -> Import Linux Kernel Symbols -> Import manually build kernel
Location:
I have this messages:
Downloading /usr/src/linux/vmlinux to D:KernelCache/Kernel_0000vmlinux... Downloading kernel files from /usr/src/linux to D:KernelCache/Kernel_0000... Cannot create D:KernelCache/Kernel_0000driversgpudrmnouveaucoresubdevi2caux.c: FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of "\." in the path. Cannot create D:KernelCache/Kernel_0000includeconfigusbsisusbvgacon.h: FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of "\." in the path. Cannot create D:KernelCache/Kernel_0000includeconfigw1con.h: FileStream will not open Win32 devices such as disk partitions and tape drives. Avoid use of "\." in the path.ViasualKernel can’t import:
– aux.c
– con.h
files.These files are present at Linux system, and successfully opens.
I don’t know for sure, but I think the Windows system reserved names might be a reason: con, nul, prn, AUX, COM1, COM2, COM3, COM4, COM5, COM6, COM7, COM8, COM9, LPT1, LPT2, LPT3, LPT4, LPT5, LPT6, LPT7, LPT8, LPT9.
Thanks.
Hi,
Unfortunately this is a limitation of Windows. Although we could workaround it by using UNC names internally, Visual Studio will still not be able to open those files. Please note that this should not affect your build: the kernel is built on the Linux system and those files will simply not be overwritten. Please let us know if you encounter some of files with reserved names that are essential for debugging. We will then add support for renaming them during import (e.g. con_.h) and seamlessly mapping the names during file transfer and debugging. This is bit cumbersome, however it looks like the only way to work around the Windows/VS limitation.
- You must be logged in to reply to this topic.