Displaying 7 results from an estimated 7 matches for "archivenam".
Did you mean:
archivename
2016 Feb 03
2
[RFC] Error handling in LLVM libraries.
...t to
tell us that the object that it's in is part of an archive, so the best
diagnostic we could produce is "In foo.o: malformed load command at index
N". A (straw-man) improved system might look like this:
class ObjectError ... { // <- Root of all object-file errors
std::string ArchiveName = "";
std::string ObjectName = "";
std::error_code EC;
void log(raw_ostream &OS) const override {
if (!ArchiveName.empty())
OS << "In archive '" << ArchiveName << "', ";
OS << "In object file '...
2012 Jun 10
1
HELP: ff package
I use the ff-package for large data and have good success in session. To
ensure my data is available for the next R session, I save my workspace and
use the /ffsave/ command to archive my large data objects. Syntax is
simple:
> ffsave(file="~/path/archiveName", list="objectName")
when I have multiple files to save, the list is expanded using c(). When I
start a new R session, I load the ff-package again and use /ffload/ to
retrieve my data. Syntax is simple:
> ffload(file="~/path/archiveName", list="objectName")...
2016 Feb 03
2
[RFC] Error handling in LLVM libraries.
...n is part of an archive, so the best
>> diagnostic we could produce is "In foo.o: malformed load command at index
>> N". A (straw-man) improved system might look like this:
>>
>> class ObjectError ... { // <- Root of all object-file errors
>> std::string ArchiveName = "";
>> std::string ObjectName = "";
>> std::error_code EC;
>>
>> void log(raw_ostream &OS) const override {
>> if (!ArchiveName.empty())
>> OS << "In archive '" << ArchiveName << "...
2016 Feb 03
6
[RFC] Error handling in LLVM libraries.
...ject that it's in is part of an archive, so the best
> diagnostic we could produce is "In foo.o: malformed load command at index
> N". A (straw-man) improved system might look like this:
>
> class ObjectError ... { // <- Root of all object-file errors
> std::string ArchiveName = "";
> std::string ObjectName = "";
> std::error_code EC;
>
> void log(raw_ostream &OS) const override {
> if (!ArchiveName.empty())
> OS << "In archive '" << ArchiveName << "', ";
> OS...
2016 Feb 03
2
[RFC] Error handling in LLVM libraries.
...ive, so the best
>>> diagnostic we could produce is "In foo.o: malformed load command at index
>>> N". A (straw-man) improved system might look like this:
>>>
>>> class ObjectError ... { // <- Root of all object-file errors
>>> std::string ArchiveName = "";
>>> std::string ObjectName = "";
>>> std::error_code EC;
>>>
>>> void log(raw_ostream &OS) const override {
>>> if (!ArchiveName.empty())
>>> OS << "In archive '" << Archiv...
2002 May 04
0
mysterious connection breakdown
...tering interactive session.
debug1: fd 1 setting O_NONBLOCK
> this is strange, there should be a message "+++ ... Beginne Backup"
> there should also be messages inserted for debugging purposes
> after all, there are three lines of output missing
+ echo starting
+ read filesystem archivename taroptions
+ echo filter comment
Disconnecting: Corrupted check bytes on input.
> !!! This usually points to a CRC compensation attack but this is
> rather unlikely since it's an internal server.
debug1: Calling cleanup 0x8065650(0x0)
[...]
----- End forwarded message -----
Any hints?...
2016 Feb 03
13
[RFC] Error handling in LLVM libraries.
Hi All,
I've been thinking lately about how to improve LLVM's error model and error
reporting. A lack of good error reporting in Orc and MCJIT has forced me to
spend a lot of time investigating hard-to-debug errors that could easily
have been identified if we provided richer error information to the client,
rather than just aborting. Kevin Enderby has made similar observations
about the