search for: salvaged

...age first-block count-blocks Salvage tries to salvage files found in blocks starting from first-block and then totally count-block blocks. if count-blocks is 0, or greater than the number of blocks in the file system, it is set to the number of blocks in the fs. typical use: cd directory-to-hold-salvaged-files path/debugfs /dev/damaged-file-system salvage 1 0 salvage could be useful if you have accidently remoded a lot of files in a ext2/ext3 file system like with a "rm -rf /" command, or if you accidently reformatted the file system via an mkfs/mke2fs command, or if your harddisk had se...

...the default concise dbg.value with a single argument and empty DIExpression, but salvaging becomes more brittle. If we rely on elements being on the stack in their declared order, then we need to guarantee that nothing modifies those stack elements. The cleanest implementation of this would be for SalvageDebugInfo to salvage expressions normally when the last register is salvaged, and switch to using DW_OP_pick for every register whenever any other register is salvaged: %c = add %a, 5 %e = div %c, %d ; x = %b * ((%a + 5) / %d) dbg.value(!DILocalVariable("x"), !DIExpression(DW_OP_mul), %b,...

...ocation is dropped causing a reduction in coverage. One of the key restrictions on this process at the moment is that each intrinsic can only reference a single SSA value; a numeric constant may be represented within the expression itself, allowing for binary operators with a constant operand to be salvaged: %c = add i32 %a, 4 llvm.dbg.value(metadata i32 %c, DILocalVariable("x"), DIExpression()) ; Salvage... llvm.dbg.value(metadata i32 %a, DILocalVariable("x"), DIExpression(DW_OP_constu, 4, DW_OP_plus)) This proposal is to allow multiple SSA value references within a debug intrin...

...ession > >If we do it this way and allow 0-n SSA values then I'm in support of the push-first scheme. This seems like as good a case as any to go with the push-first approach, since it solves a meaningful problem that the alternative does not. >As a side note, updating dbg.values in salvageDebugInfo when we allow multiple SSA values per dbg.value will be interesting, but possible. We'll need to put the value we need to update at the top of the stack, prepend the salvage expression and then restore the order of arguments on the stack that the rest of the expression expects. The dif...

Somehow my workstations lost their connection to the domain recently. I can rejoin them, but when I leave the domain and rejoin the previous user profiles are lost. Well, the data is still on the system, but all pre-rejoin domain profiles are listed as "account unknown" in the profile manager. I know I can probably use the Files and Settings Transfer Wizard on the XP machines as long

For years, I could install, and sometimes run, legacy private map software under Wine. But in order to connect it with my GPSs, I had to keep a separate hard drive with XP, and do that there. Then came a brief time when I could also actually make my Garmin GPSs talk with the software under Wine. I transferred all my data to it, and gleefully wiped XP off my machine. Then the connecting

I encountered something a little strange today. Previously I had enabled samba logging and forgot to disable it. Unsurprisingly my /var partition maxed out. To correct this, I disabled the logging and deleted the (approx 240 MB) samba log file. Strangely I still had a full /var partition. Running df gave me: SRV04# df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/ad4s1a

Hi Djordje, [Late reply as I was away, alas], For the example in https://reviews.llvm.org/D85012 , I'm not sure that just using an entry value is correct. The reason why the dbg.values for arguments are set to undef is not because the value can't be described, it's because deadargelim changes all the call sites to pass in 'undef', which I believe makes the value unrecoverable

Hi Djordje, On Wed, Sep 9, 2020 at 7:52 AM Djordje Todorovic <Djordje.Todorovic at syrmia.com> wrote: > Using entry-values ('callee' side of the feature) is not enough in any case. It is always connected to the call-site-param (function arguments but we call it call-site-params; 'caller' side of the feature) debug info. I believe that there are call-site-params that could

...trol arrays. I am pretty well versed in the analysis of array data using R, but obviously this dataset presents a real challenge because of the low replication. For logistical reasons, increasing the sample size is not a possibility. My main goal here is to salvage whatever valid findings can be salvaged from the existing data, but I dont want to go too far in claiming significance for an expression pattern if there isnt really anystatistical support for it. My questions are: (1) Whether it is even possible to statistically compare the effects of these stressors on gene expression, (2) If so, what...

Hi ! I'd like to know how does Samba delete files, because I need do something to instead Samba removes files, it moves the deleted files to another directory, like a Netware Salvage File or a Windows Trash Can. Thanks, Bruno Stella brunostella@trt15.gov.br Setor de Redes - Secretaria de Informatica Tribunal Regional do Trabalho da 15a. Regiao

Hello, VERSIONS tried: 3.0.9 and 3.0.10 Function: Domain Controller Summary: Using the recycle vfs module, files deleted are not "touched" Details: I've set up VFS recycle so that when a user deletes a file it gets moved to the .salvage directory. recycle:touch = yes is set, but the moved (deleted) file still contains the original time stamp when doing an "ls -al".

...pace. However, this ends up > hurting performance significantly (about 4x slower than the current > new version, making it around half the speed of the version in stats). That's a clever solution! Can you profile the code to see if there are visible sources of slowdown? Maybe this can be salvaged. -- Best regards, Ivan

...post-LSR setting these dbg.value are now referring to undef so the debug-info for 'p' is effectively lost. It is interesting to note that after LSR one dbg.value has its DIExpression adjusted to add the value three but it is still referring to undef. As I understand it this is the work of salvageDebugInfo. When LSR has created the new induction variable expression and starts deleting the old one salvaging will kick in. When %add.ptr is deleted it will adjust the dbg.value use of that to use the value %p.addr.05, and by doing so it must accordingly adjust the DIExpression. This all works fine...

On Thu, Apr 06, 2017 at 08:27:47PM +0300, Ville Syrj?l? wrote: > On Thu, Apr 06, 2017 at 10:29:43AM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > > static const uint32_t virtio_gpu_cursor_formats[] = { > > > > +#ifdef __BIG_ENDIAN > > > > + DRM_FORMAT_BGRA8888, > > > > +#else > > > > DRM_FORMAT_ARGB8888, > >

On Thu, Apr 06, 2017 at 08:27:47PM +0300, Ville Syrj?l? wrote: > On Thu, Apr 06, 2017 at 10:29:43AM +0200, Gerd Hoffmann wrote: > > Hi, > > > > > > static const uint32_t virtio_gpu_cursor_formats[] = { > > > > +#ifdef __BIG_ENDIAN > > > > + DRM_FORMAT_BGRA8888, > > > > +#else > > > > DRM_FORMAT_ARGB8888, > >

I was playing around with btrfs, and did a mkfs.btrfs on one of my partition. Mistakes, it was my data partition (ext3 based). I have not yet mounted the device, but the mkfs.btrfs continued to completion. Is it possible to salvage my ext3 filesystem? Anyway to reverse the effect of mkfs.btrfs? Thank you for your help/answer. -- Regards, Peter Teoh

...ould > recover an implicit variable value, if you could for example subtract > one pointer from another. > > With the current model of storing DIExpressions as a vector of > opcodes, it might become a pain to salvage a Value that gets optimised > out --in the example, if %ofs were salvaged, presumably > DW_OP_LLVM_arg1 could have to be replaced with several extra > operations. This isn't insurmountable, but I've repeatedly shied away > from scanning through DIExpressions to patch them up. A vector of > opcodes is the final output of the compiler, IMHO richer metad...

...26 %add = add nsw i32 %call, %call1, !dbg !27 %sub = sub nsw i32 %add, 4, !dbg !28 call void @llvm.dbg.value(metadata i32 %sub, metadata !24, metadata !DIExpression()), !dbg !29 %mul = mul nsw i32 %sub, 2, !dbg !30 ret i32 %mul, !dbg !31 ; Combine redundant instructions, "a" is salvaged... %call = call i32 @_Z3bazv(), !dbg !25 %call1 = call i32 @_Z3barv(), !dbg !26 %add = add nsw i32 %call, %call1, !dbg !27 call void @llvm.dbg.value(metadata i32 %add, metadata !24, metadata !DIExpression(DW_OP_constu, 4, DW_OP_minus, DW_OP_stack_value)), !dbg !28 %sub = shl i32 %add, 1,...

...a over the network. This problem occurs after a file has been worked on and someone attempts open a file that they were working on. There is no indication of a problem while the file is open and being worked on. But when they try to re-open it, autocad thinks the file is corrupt and it cannot be salvaged. Our autocad dealer has suggested that it could be a problem with the NIC but I have run diagnostics on server and client NIC's and found no problem. -- Bob