search for: throwerror

...c.a-000003' to './libgcc.a-000002': Cannot create a file when that file already exists. So apparently, we're trying to move one file on top of another. The error is generated in: Path::renamePathOnDisk(const Path& newName) { if (!MoveFile(path.c_str(), newName.c_str())) ThrowError("Can't move '" + path + "' to '" + newName.path + "': "); return true; } I'm guessing that the last part of the error message ("Cannot create a file when that file already exists") is the result of a GetLastError() ?...

...0002': Cannot create a file when that file already exists. > > So apparently, we're trying to move one file on top of another. > > The error is generated in: > > Path::renamePathOnDisk(const Path& newName) { > if (!MoveFile(path.c_str(), newName.c_str())) > ThrowError("Can't move '" + path + > "' to '" + newName.path + "': "); > return true; > } > > I'm guessing that the last part of the error message ("Cannot create a > file when that file already exists") is the...

Hi Reid, The error still exists. However, looking on the function in Win32/Path.cpp: -------------- void sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } -------------- I notice, that the function is living in the sys namespace. Shouldn't it live in the Path class instead? A copy-past to fast ;-) Henrik. __...

...ots of issues with 'permission denied' or 'network not found' and so forth when reading and writing between our machines and a file server. This happens randomly so the following function solves the problem for 'cat' commands: catSafer <- function (..., ReTries = 20, ThrowError = TRUE) { for (catsi in seq_len(ReTries)) { res <- try(cat(...)) if (!inherits(res, "try-error")) break } if (inherits(res, "try-error")) { if (ThrowError) { stop("file connection failed")...

...t 15:48, Henrik Bach wrote: > Hi Reid, > > The error still exists. However, looking on the function in Win32/Path.cpp: > -------------- > void > sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { > if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) > ThrowError("Can't copy '" + Src.toString() + > "' to '" + Dest.toString() + "'"); > } > -------------- > > I notice, that the function is living in the sys namespace. Shouldn't it > live in the Path class instead? A copy-...

...eference to `llvm::sys::CopyFile(llvm::sys::Path const&, llvm::sys::Path const&)' collect2: ld returned 1 exit status --------------- Path.cpp: --------------- void CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } --------------- Henrik. ============================================================= Henrik Bach Open Source Developer e-mail: henrik_bach_llvm at hotmail.com...

...th const&, llvm::sys::P Date: Fri, 24 Dec 2004 00:48:26 +0100 Hi Reid, The error still exists. However, looking on the function in Win32/Path.cpp: -------------- void sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } -------------- I notice, that the function is living in the sys namespace. Shouldn't it live in the Path class instead? A copy-past to fast ;-) Henrik. __...

...gt; >>Hi Reid, >> >>The error still exists. However, looking on the function in Win32/Path.cpp: >>-------------- >>void >>sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { >> if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) >> ThrowError("Can't copy '" + Src.toString() + >> "' to '" + Dest.toString() + "'"); >>} >>-------------- >> >>I notice, that the function is living in the sys namespace. Shouldn't it >>live in the Path clas...

...#39;re done. if (attr == INVALID_FILE_ATTRIBUTES) return true; // Read-only files cannot be deleted on Windows. Must remove the read-only // attribute first. if (attr & FILE_ATTRIBUTE_READONLY) { if (!SetFileAttributes(path.c_str(), attr & ~FILE_ATTRIBUTE_READONLY)) ThrowError(path + ": Can't destroy file (hb:1): "); } if (!DeleteFile(path.c_str())) ThrowError(path + ": Can't destroy file (hb:2): "); return true; } ------------------------- I've also attached a complete trace for this run. Any suggestions? Henrik. __________...

...th const&, llvm::sys::P Date: Fri, 24 Dec 2004 00:48:26 +0100 Hi Reid, The error still exists. However, looking on the function in Win32/Path.cpp: -------------- void sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) ThrowError("Can't copy '" + Src.toString() + "' to '" + Dest.toString() + "'"); } -------------- I notice, that the function is living in the sys namespace. Shouldn't it live in the Path class instead? A copy-past to fast ;-) Henrik. __...

Completed testing. Diffs for Path.cpp attached to fix bugs. Some of them are probably present in the Unix version as well. There are some uses of ThrowError when there is no error present in errno to format. A throw statement should be used. Path::is_valid uses realpath on Unix. The problem is that realpath validates that all the directory components of the path actually exist and are executable. There are two problems with this. First, Path.h sta...

...; Consider this a down payment :) The Win32 version of Memory.cpp attached. On further reflection, I think we need to abstract the operation of throwing a formatted OS error message. This is done in many places, and the Windows way of doing it differs substantially from Unix. Basically take the ThrowError function and turn it into Process::ThrowOSError or something like that.

...c 2004 00:48:26 +0100 > > Hi Reid, > > The error still exists. However, looking on the function in Win32/Path.cpp: > -------------- > void > sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { > if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) > ThrowError("Can't copy '" + Src.toString() + > "' to '" + Dest.toString() + "'"); > } > -------------- > > I notice, that the function is living in the sys namespace. Shouldn't it > live in the Path class instead? A copy-...

Patch committed. Thanks for cleaning up some of the coding standards issues. Reid. On Sat, 2004-09-18 at 22:18, Jeff Cohen wrote: > Patch for Signals.cpp attached. > > On Sat, 18 Sep 2004 21:30:12 -0700 > Jeff Cohen <jeffc at jolt-lang.org> wrote: > > > On Sat, 18 Sep 2004 12:30:41 -0700 > > Reid Spencer <reid at x10sys.com> wrote: > > > >

On Mon, 13 Sep 2004 20:54:57 -0700 Reid Spencer <reid at x10sys.com> wrote: > On the other hand, no one has submitted any Win32 patches yet, so first > come first served :) > > Reid. Consider this a down payment :) The Win32 version of Memory.cpp attached. -------------- next part -------------- A non-text attachment was scrubbed... Name: Memory.cpp Type:

...Path const&, llvm::sys::Path const&)' > collect2: ld returned 1 exit status > --------------- > > Path.cpp: > --------------- > void > CopyFile(const sys::Path &Dest, const sys::Path &Src) { > if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) > ThrowError("Can't copy '" + Src.toString() + > "' to '" + Dest.toString() + "'"); > } > --------------- > > > Henrik. > > ============================================================= > Henrik Bach > Open Source...

Its version 1.27 of lib/System/Unix/Path.cpp for Cygwin and version 1.22 of lib/System/Win32/Path.cpp for Win32 Please note that 1.22 of Win32/Path.cpp was *just* committed. I fixed the Unix side, but not the Win32 side until just now. Sorry about that. Promise to get better about this soon (more machines to test on). Reid. On Thu, 2004-12-23 at 14:06, Henrik Bach wrote: > Hi Reid, >

Hi Reid, >Get the latest version. I committed a fix to Path.cpp last night. It >wasn't being defined in the sys:: namespace which is why its undefined. It didn't do any better by removing the old debug files, getting the latest version and reconfiguration of the build. No diffs of Path.cpp and gccld.cpp against top of mainline were were found. Henrik.

...gt; >>Hi Reid, >> >>The error still exists. However, looking on the function in Win32/Path.cpp: >>-------------- >>void >>sys::CopyFile(const sys::Path &Dest, const sys::Path &Src) { >> if (!::CopyFile(Src.c_str(), Dest.c_str(), false)) >> ThrowError("Can't copy '" + Src.toString() + >> "' to '" + Dest.toString() + "'"); >>} >>-------------- >> >>I notice, that the function is living in the sys namespace. Shouldn't it >>live in the Path clas...

Here are some more... and that takes care of the easy ones. Path I'll wait on until you finish updating it. Signals is a problem... It appears to be doing two tasks. First, it prints a stack trace when something like a seg fault occurs. Second, it makes sure a set of files and directories are deleted on an abnormal exit. The first is no problem. It won't even be necessary to fork