similar to: strange mangled name

I just took on a new client who is having a curious problem with mangled names. Here's the history as I understand it: Originally they were on an NT server and there was no issue. My predecessor moved them to a samba server running on gentwo. I do not know what version of samba or how he moved the data, but when he did so, any files and folders with more than 8 characters started

I have encountered a need for manually generating the mangled name of an arbitrary C++ function. The only way I currently know how to do this is to generate a dummy C++ source file, compile it, and look at the output. This approach is so ugly that I would like for it never to see the light of day. The c++filt tool generates demangled C++ names given the mangled ones, which is the opposite

On Feb 15, 2011, at 3:10 AM, Patrick Simmons wrote: > I have encountered a need for manually generating the mangled name of an > arbitrary C++ function. The only way I currently know how to do this is > to generate a dummy C++ source file, compile it, and look at the > output. This approach is so ugly that I would like for it never to see > the light of day. The c++filt tool

I believe that I've found a bug on Samba 2.2.3a. Sure, there is the 2.2.5 version out there, but reading the changelog I couldn't find something that looked like what I've found. Problem is: Some files (very few of them, about 0,5%) are created, with 2 another copies. The file witch would be the real one is perfect. And we got "for free" 2 corrupted copies of it, with

Hi all, while working with Netbench I've discovered that mangled directory names clash rather frequently with Samba 2.2.4: If I take an NT box, open the cmd prompt and make the following directories on a Samba share, client100 and client121, both mangle to CLIEN~GH. If I create directories client100 through client130 I see 11 clashes altogether: CLIEN~GH: client100 client121 CLIEN~MF:

Hello, after upgrade Samba from 1.9.17p4 to 2.0.7 I have problems with name mangling. Changed parameters in SMB.CONF for new version: oplocks = no client code page = 852 local master = yes all other parameters are the same. I one directory I have these files: 0011_BAR_ISSUEAGRES.CSV 0011_MIR_STKGEN.CSV 0011_OLO_ISSUEMPSPEC.CSV 0011_RET_ISSUEAGRES.CSV When I look to these files (DIR /X) from

Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. It seems to be happening when I use vnd.dovecot.filter. When I comment out the block, things come through fine. My filter block looks like this: require "vnd.dovecot.filter"; filter "bogofilter_filter"; if header :contains "X-Bogosity" [ "Spam,

Hi folks, I am having a problem rsyncing files with accents in the names. I've seen similar problems reported a few times before in the archives but they didn't seem to be referring to exactly the same problem as what I have, and I'm not good enough at Linux to solve my problem by generalising from the information there: sorry. Anyway, my specific details are this. I am running rsync

Let me first apologise for asking on two lists, but this problem is (of course) urgent because prior to this afternoon I was unaware of the problem and it has been affecting production users for two days despite me having warned everyone that they should be looking out for possible Samba problems! I have just upgraded most of our samba servers from 1.9.18 (various patch levels) to 2.2.2 on

Op 1/20/2018 om 11:01 PM schreef Adam Weinberger: >> On 20 Jan, 2018, at 10:05, Adam Weinberger <adamw at adamw.org> wrote: >> >> >>> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>> >>> >>> >>> On 19.01.2018 04:35, Adam Weinberger wrote: >>>> Since upgrading to 2.3.0 / 0.5.0.1, incoming

Hi all, I run samba 3.6.6 from debian wheezy (version 3.6.6) and i am experiencing some troubles with file name mangling. If i try "dir /x" on a mapped folder it gives me unexpected mangled names: the name mangling matches only the first character and not the first 5 as i expect. For example: if the long file name is LONGFILENAME.TXT, i expect the mangled sholud be something like

I want all the file-names to be stored on a samba share from my XP clients to be automatically converted to 8.3 syntax, so that i do not have any further problem while transporting those files over to other networks/servers like netware. As for now i am using these below mentioned lines to support file-name mangling over my samba. --------- #I do not want my filenames to be case sensitive,

+ Alexey Anastasia According to SPIR spec v1.2 s2.10.3 2.10.3 The printf function The printf function is supported, and is mangled according to its prototype as follows: int printf(constant char * restrict fmt, ... ) Note that the ellipsis formal argument (...) is mangled to argument type specifier z It seems printf should be mangled. Alexey/Anastasia, What do you think? Thanks. Sam From:

Thanks a lot. On Mon, Sep 12, 2016 at 1:42 PM, Liu, Yaxun (Sam) <Yaxun.Liu at amd.com> wrote: > If you use the default header file under clang/lib/Headers/opencl-c.h, > get_global_id will be mangled. > > > > If you want to declare get_global_id in your own header, add > __attribute__((overloadable)), then it will be mangled. > > > > Sam > > > >

> On 19 Jan, 2018, at 4:39, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > > On 19.01.2018 04:35, Adam Weinberger wrote: >> Since upgrading to 2.3.0 / 0.5.0.1, incoming PDFs are getting mangled. >> It seems to be happening when I use vnd.dovecot.filter. When I comment >> out the block, things come through fine. >> >> My filter block looks like

I've installed Samba 3.0.7 (stock Debian package), but I'm having some wierd problems with name mangling. The relevant lines in smb.conf are: preserve case = yes short preserve case = yes mangled names = yes mangle prefix = 5 mangling method = hash2 In a share, I did "touch test-file.GHO" to create a long filename. When I do a "dir" under DOS,

I don't see any problem mangling it to be honest even though there seems to be only one prototype anyways. We could add restrict in as well. Cheers, Anastasia ________________________________ From: Hongbin Zheng <etherzhhb at gmail.com> Sent: 17 September 2016 05:32:54 To: Liu, Yaxun (Sam) Cc: cfe-dev at lists.llvm.org; llvm-dev; Bader, Alexey (alexey.bader at intel.com); Anastasia

Hi all, According to the SPIR 2.0 spec[1], the name of OpenCL builtins are mangled. However, when I compile OpenCl code with Clang 3.9 with the "spir64-unknown-unknown" target, Clang generates IR without mangling the builtins, e.g. for: __kernel void input_zip_int(__global int *in0) { *in0 = get_global_id(0); } clang generates: define spir_kernel void @input_zip_int(i32

HTML attachment scrubbed and removed -------------- next part -------------- A non-text attachment was scrubbed... Name: klaus.troeger.vcf Type: text/x-vcard Size: 331 bytes Desc: Card for Klaus Troeger Url : http://lists.samba.org/archive/samba/attachments/20000630/dedb54e2/klaus.troeger.vcf

I just want to warn people that want to use the new hashing algorithm for mangled names. And that note should also be put in the man page IMO. You must understand that changing the hashing algorithm on a production server may have unwanted side effects (this is why we maintain by default hash and not hash2 and why it was not back ported to 2.2 initially). Windows clients may save all around