search for: path_to_directory

...e from a cygwin based rsync to a MingW based version. 'rsync' is used here to install/update a complete TeX tree (see http://wiki.contextgarden.net/ConTeXt_Standalone) from a remote server to a local PC. On Windows based machines the destination is currently something like /cygdrive/c/<path_to_directory> What is the correct way to do the same with the MingW version? I've tried some options, but I'm not quite sure, what is the correct syntax here. 1. /c/<path_to_directory> 2. /c:/<path_to_directory> 3. '--files-from' should work too, but is a bit cumbersome...

Hi, I am working on a project where I have to move some parts files from an old Unix server. I have tared the files to floppy disc, but I can't mount them. After doing some reasearch I have found that the SCO Unix ver 3.2 uses a System V filesystem I think. From the article that I have read I need to add this filesystem to my kernel to be able to mount and read the floppy discs. Can

...3, subprograms: !12, globals: !54) ... !12 = !{!13} !13 = distinct !DISubprogram(name: "main", scope: !14, file: !14, line: 15, type: !15, isLocal: false, isDefinition: true, scopeLine: 15, isOptimized: true, variables: !17) !14 = !DIFile(filename: "main.c", directory: "path_to_directory") ... !68 = !DILocalVariable(name: "d", arg: 1, scope: !69, file: !14, line: 9, type: !11) !69 = distinct !DISubprogram(name: "delay", scope: !14, file: !14, line: 9, type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags: DIFlagPrototyped, isOptimized: true,...

...3, subprograms: !12, globals: !54) ... !12 = !{!13} !13 = distinct !DISubprogram(name: "main", scope: !14, file: !14, line: 15, type: !15, isLocal: false, isDefinition: true, scopeLine: 15, isOptimized: true, variables: !17) !14 = !DIFile(filename: "main.c", directory: "path_to_directory") ... !68 = !DILocalVariable(name: "d", arg: 1, scope: !69, file: !14, line: 9, type: !11) !69 = distinct !DISubprogram(name: "delay", scope: !14, file: !14, line: 9, type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags: DIFlagPrototyped, isOptimized: true,...

..... > > !12 = !{!13} > > !13 = distinct !DISubprogram(name: "main", scope: !14, file: !14, line: > 15, type: !15, isLocal: false, isDefinition: true, scopeLine: 15, > isOptimized: true, variables: !17) > > !14 = !DIFile(filename: "main.c", directory: "path_to_directory") > > ... > > !68 = !DILocalVariable(name: "d", arg: 1, scope: !69, file: !14, line: 9, > type: !11) > > !69 = distinct !DISubprogram(name: "delay", scope: !14, file: !14, line: > 9, type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags:...

..... > > !12 = !{!13} > > !13 = distinct !DISubprogram(name: "main", scope: !14, file: !14, line: > 15, type: !15, isLocal: false, isDefinition: true, scopeLine: 15, > isOptimized: true, variables: !17) > > !14 = !DIFile(filename: "main.c", directory: "path_to_directory") > > ... > > !68 = !DILocalVariable(name: "d", arg: 1, scope: !69, file: !14, line: 9, > type: !11) > > !69 = distinct !DISubprogram(name: "delay", scope: !14, file: !14, line: > 9, type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags:...

...!12, globals: !54) > ... > !12 = !{!13} > !13 = distinct !DISubprogram(name: "main", scope: !14, file: !14, line: 15, type: !15, isLocal: false, isDefinition: true, scopeLine: 15, isOptimized: true, variables: !17) > !14 = !DIFile(filename: "main.c", directory: "path_to_directory") > ... > !68 = !DILocalVariable(name: "d", arg: 1, scope: !69, file: !14, line: 9, type: !11) > !69 = distinct !DISubprogram(name: "delay", scope: !14, file: !14, line: 9, type: !70, isLocal: true, isDefinition: true, scopeLine: 9, flags: DIFlagPrototyped, isOptim...

I'm not as familiar with all the ins and outs of metadata as maybe I should be, but ultimately the inlined function should have a DWARF description contained within the description of the caller (which is why you're seeing the call to constructAbstractSubprogramScopeDIE). That suggests that the DISubprogram for the inlined function ought to remain, and its scope should be the

Hi all, I would like to understand the strip-dead-debug-info transformation. In my test case there is a static inline function with two local variables. It appears that the function is already inlined before strip-dead-debug-info starts its work. As a result the DICompileUnit is cleaned and its subprograms list has no reference to the DISubprogram for the inlined function, but as there is