similar to: once again: [Too many errors (client not receiving data fast enough)]

Hello folks, when using Darkice to send a stream to an Icecast 1 server, the icecast administration page is not updated correctly.The mountpoint etc.. is all there, but the name of the darkice stream is not there. It has been replaced with the name of the default stream for the server. To ensure I had not overlooked anything, I had also tried the same thing with MuSE, and the same behaviour was

I'm having problems with Windows XP clients losing connections to the Samba server and also, connecting very slowly. Getting the following error in the logs: [2003/09/05 08:47:02, 0] lib/util_sock.c:read_data(436) read_data: read failure for 4. Error = Connection reset by peer This error is only generated by the Windows XP machines. The Windows 98 boxen work fine. Here's the details

> On Jul 22, 2016, at 7:28 PM, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > >> On Jul 22, 2016, at 12:31 AM, David Chisnall <David.Chisnall at cl.cam.ac.uk> wrote: >> >> On 22 Jul 2016, at 07:14, Mehdi Amini via llvm-dev <llvm-dev at lists.llvm.org> wrote: >>> >>> Just tried to set it up there:

Hello all, I recently finished merging the last 3.5 months of upstream changes into our CHERI LLVM fork and would like to suggest something to both simplify our future merges and also avoid bugs for targets such as AVR that use non-zero pointer address spaces. We make extensive use of address spaces: all our pointers (CHERI capabilities) use address space 200 instead of the default zero to

I am a newbie to samba. I have successfully setup a similar samba share on 1 machine in the past. I have everything setup as User access with the pcguest as a guest account. If I create a share to the /tmp, network users can access normally. I created a directory /var/snd and set permissions to be rwxrwxrwx. I changed the smb.conf so that permission were identical to the share for /tmp. I

I just want to point out that the issue of incompatible history is not new. This has been getting discussed all the way back in July 2016. http://lists.llvm.org/pipermail/llvm-dev/2016-July/102657.html <http://lists.llvm.org/pipermail/llvm-dev/2016-July/102657.html> As James said in that email: > That we'll be getting incompatible history has been glossed over, and it is >

Evelyn Brent's life and career were going quite well in 1928. Following her divorce from producer Bernard Fineman, she was happily living with writer Dorothy Herzog. The couple was often seen enjoying lunch at the Montmartre Caf9, and Brent had recently had a cabin built in the San Bernardino Mountains. The tiny brunette actress had wowed film fans and critics with recent appearances in the

OK, I just took my first non-root user live on my Samba 3.0.7 system. Printing is via cups, with drivers stored in the print$ share. This user is a local power user. She can add printers, or root can add them. Root can also print from them. If this user tries to print anything (a test page even) she gets a non-verbose error that looks like a permissions error. She can view the queues

https://bugzilla.mindrot.org/show_bug.cgi?id=2704 Bug ID: 2704 Summary: Avoid passing pointers between processes Product: Portable OpenSSH Version: -current Hardware: Other OS: All Status: NEW Severity: enhancement Priority: P5 Component: sshd Assignee: unassigned-bugs at

I agree, improving this makes sense. Alexander, I don’t think that “LLVM_DEFAULT_AS_PARAM” is the right way to go, I would just remove the “ = 0” default parameter entirely. -Chris > On Jul 23, 2020, at 11:02 AM, Nicolai Hähnle via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Hi Alex, > > I'd be very much in favor of this, thanks for pushing ;) > > On Wed,

> On Jul 19, 2016, at 09:52, David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > The IR disruptions for CHERI aren’t that major (the main thing is that we allow alloca’s in different address spaces, but that’s not too difficult to upstream), but it does fail to tick one box that you didn’t list: We would like this feature upstreamed -Matt -------------- next part

Well shoot, you beat me to it. :) I've been working on a similar tool but it's not ready yet. Looking forward to trying yours! -David James Y Knight via llvm-dev <llvm-dev at lists.llvm.org> writes: > I'm about to post exactly this tool -- I've been testing it on the > CHERI forks of llvm/clang/lld (lots of history and merges and stuff

On 17 Mar 2015, at 13:11, Tyro Software <softwaretyro at gmail.com> wrote: > > As an alternative to fixing the "char == 8 bits" presumption would using non-uniform pointer types have been another possible approach, e.g. keep char as 8 bit but have char* encode both the word address and the byte location within it (i.e. one extra bit in this 16-bit case). Of course this is

On 26 Dec 2017, at 10:13, Bhatu via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > According to my understanding, it seems that the result of realloc will not technically alias the original pointer. When the realloc is done in-place the reference says: > "The original pointer ptr is invalidated and any access to it is undefined behavior (even if reallocation was

On Fri, 1 Feb 2019 at 20:35, Matt Arsenault <arsenm2 at gmail.com> wrote: > Oh right, you don’t have the addrspace in the input. Input to what? Even if it's available it's wrong without a fixup pass. Still, custom override for GEP as you talk about later could overcome the problem... > I have long wanted a way for targets to take over the GEP expansion which may help you?

connecting legacy PBX to Asterisk (for the very same reason, those PBX use TE-PTMP). If others could join this thread and say if they agree or not with NT-PTMP being the 2nd most needed mode, would be great. Please, do not hesitate to comment. > > > Right now, I would not preclude the possibility that NT-PTMP support > might be added, but I could not give you a concrete time at which

> Note that InstCombine is not the only place that tries to insert pointer-width GEPs in the optimization pipeline. I think that we’ve fixed all of them, but I can’t be entirely sure. I'm going to upload a patch, but I'm fixing only the places that are covered by our test system. I'll add you as a reviewer and you are welcome to help me with fixing them all. > We haven’t

Moving to llvmdev, as this is not a clang issue. David > Begin forwarded message: > > Date: 5 February 2015 17:00:34 GMT > From: Sean Bruno <sbruno at ignoranthack.me> > To: cfe-dev at cs.uiuc.edu > Subject: [cfe-dev] freebsd-mips64 unhandled .cpsetup > Reply-To: sbruno at freebsd.org > > > I'm taking a journey to try and get a clang/llvm build of

Hello the lists, Please feel free to ignore this message if you are not in Cambridge. As previously mentioned, we are hosting an afternoon LLVM workshop in the Computer Lab on Monday (15th). We'll start in the morning with a tutorial and then have 15-minute talks with 5 minutes for questions and speaker changeover in the afternoon. The event is open to all and will be in room FW11 of the

LLVM makes several assumptions about address space 0. However, alloca is presently constrained to always return this address space. There's no real way to avoid using alloca, so without this there is no way to opt out of these assumptions. The problematic assumptions include: * That the pointer size used for the stack is the same size as the code size pointer, which is also the