search for: mortem

Displaying 20 results from an estimated 604 matches for "mortem".

Did you mean: morten
2011 Oct 11
0
Post Mortem 1 huge grafical issues
Hi everybody, The Game Post Mortem 1 is unplayable in my wine. This is causing by huge grafical issues. Items are not correct drawn and People "flashes". Here is waht the Console says: Code: pingi at 16L:/media/32GB-usb3/Spiel_1/Programme/Microids/Post Mortem$ wine "Post Mortem.exe" fixme:win:EnumDisplayDevice...
2014 Mar 21
1
windigo post-mortem
ESET recently published an interesting post-mortem of the so-called "Operation Windigo" malware campaign [1]. OpenSSH backdoors (codename Linux/Ebury), described by ESET last month [2], are a key component of Windigo's attack surface. --mancha [1] http://www.welivesecurity.com/wp-content/uploads/2014/03/operation_windigo.pdf [2] ht...
2016 Nov 14
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
>>>>> nospam at altfeld-im de <nospam at altfeld-im.de> >>>>> on Sun, 13 Nov 2016 13:11:38 +0100 writes: > Dear R friends, to allow post-mortem debugging In my > Rscript based batch jobs I use > tryCatch( <R expression>, error = function(e) { > dump.frames(to.file = TRUE) }) > to write the called frames into a dump file. > This is similar to the method recommended in the "Writing >...
2016 Nov 13
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
Dear R friends, to allow post-mortem debugging In my Rscript based batch jobs I use tryCatch( <R expression>, error = function(e) { dump.frames(to.file = TRUE) }) to write the called frames into a dump file. This is similar to the method recommended in the "Writing R extensio...
2016 Nov 15
0
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
...simple use of the above, "g" is clearly available in the .GlobalEnv component of last.dump : > exists("g", last.dump$.GlobalEnv) [1] TRUE > get("g", last.dump$.GlobalEnv) [1] "global" > and that's all what's promised, right? In such a post mortem debugging, notably from a batch job (!), you don't want your .GlobalEnv to be *replaced* by the .GlobalEnv from 'last.dump', do you? I think in the end, I think you are indirectly asking for new features to be added to debugger(), namely that it works more seemlessly with a last.dump...
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> Bash 2.05b on Linux handles this fine. I was asking what > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > Perhaps you can: > > SHELL=/usr/bin/bash ; export SHELL > > in your script below just before it runs NightlyTest.pl? I'm not sure if > that will work or not. I have: SHELL=/bin/tcsh sh, csh, tcsh not support nested () OK, root
2004 Sep 09
0
[LLVMdev] POST MORTEM: llvm-test changes
On Sun, 05 Sep 2004 14:02:26 -0700 Reid Spencer <reid at x10sys.com> wrote: > > Assertion failed: ((FieldSizeTree != NULL_TREE) && "Struct/Union member of unknown length!"), function llvm_expand_constructor_elements, file ../../src/gcc/llvm-expand.c, line 3791. > > /usr/home/llvm/obj/../test/Regression/CFrontend/2004-01-01-UnknownInitSize.c:11: internal compiler
2004 Sep 10
0
[LLVMdev] POST MORTEM: llvm-test changes
On Thu, 9 Sep 2004 08:52:10 -0700 Jeff Cohen <jeffc at jolt-lang.org> wrote: > > I haven't got around to this yet but I will. The odds are good the > > problem is in a BSD system header file so I need to capture the > > preprocessed source. > > I guess not... the file 2004-01-01-UnknownInitSize.c does not include > anything else, so there is no preprocessed
2004 Sep 09
2
[LLVMdev] POST MORTEM: llvm-test changes
> I haven't got around to this yet but I will. The odds are good the > problem is in a BSD system header file so I need to capture the > preprocessed source. I guess not... the file 2004-01-01-UnknownInitSize.c does not include anything else, so there is no preprocessed source to capture...
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> x86 FreeBSD: > * hasn't run with changes yet I manually start script. I use this options (+ -verbose now for testing) /home/wanderer/pkg/build/llvm/src/llvm/utils/NightlyTest.pl -parallel -enable-linscan -noexternals -noremove :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm /home/wanderer/pkg/build/llvm/night/build
2016 Nov 15
2
Missing objects using dump.frames for post-mortem debugging of crashed batch jobs. Bug or gap in documentation?
...ense to unify the semantics? THX! On Mon, 2016-11-14 at 11:34 +0100, Martin Maechler wrote: > >>>>> nospam at altfeld-im de <nospam at altfeld-im.de> > >>>>> on Sun, 13 Nov 2016 13:11:38 +0100 writes: > > > Dear R friends, to allow post-mortem debugging In my > > Rscript based batch jobs I use > > > tryCatch( <R expression>, error = function(e) { > > dump.frames(to.file = TRUE) }) > > > to write the called frames into a dump file. > > > This is similar to the method r...
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
Actually, I'm talking about the shell that Perl invokes. When you run the NightlyTest.pl script, it uses Perl. The system() function in Perl invokes the "standard" shell to execute the command provided as the argument to system(). In NightlyTest.pl, I have changed the program to check out both the regular llvm CVS module as well as the llvm-test module. This command is what is
2004 Sep 05
0
[LLVMdev] POST MORTEM: llvm-test changes
> That's weird. What is your default shell that Perl invokes with the > "system" command. This works fine with bash-2.05b. In reality :) i use this script in crontab (and run it manually with added verbose flag): ---8X-------------- #!/bin/sh - # if !([ -d /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD ]) then mkdir
2002 Aug 19
1
PR#1914
...000 0091ef40 00482a81 017a2360 00000022 00f2da40 > version _ platform i386-pc-mingw32 arch i386 os mingw32 system i386, mingw32 status major 1 minor 5.1 year 2002 month 06 day 17 language R (2) I see no request in either the RWinFAQ or the RFAQ for a post-mortem dump. I also see no link in the R-Bugs page to the either of these FAQs, nor a list of bugs that should not be reported. If you wish users to follow a specific protocol for reporting bugs (and the RFaq section 9 does not request port-mortem dumps, or list bugs nots to report), specifying this proto...
2004 Sep 06
0
[LLVMdev] POST MORTEM: llvm-test changes
After fixing nested () problem manual run nighttest finished successfully with one remarkable logged problem: INITIALIZED CVS Root = :pserver:anon at llvm-cvs.cs.uiuc.edu:2401/var/cvs/llvm BuildDir = /home/wanderer/pkg/build/llvm/night/build WebDir = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD Prefix = /home/wanderer/pkg/build/llvm/night/testresults-X86-FreeBSD/2004-09-06
2004 Sep 05
3
[LLVMdev] POST MORTEM: llvm-test changes
Okay, I'll have to fix NightlyTest.pl not to use shell script syntax that isn't universal. Look for a commit soon. Reid. On Sun, 2004-09-05 at 13:31, Vladimir Merzliakov wrote: > > Bash 2.05b on Linux handles this fine. I was asking what > > your "default" system shell is on FreeBSD. Probably /bin/sh, right? > > Perhaps you can: > > > >
2017 May 04
1
R 3.4.0 for Ubuntu zesty?
...t voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance Kliniekstraat 25 1070 Anderlecht Belgium To call in the statistician after the experiment is done may be no more than asking him to perform a post-mortem examination: he may be able to say what the experiment died of. ~ Sir Ronald Aylmer Fisher The plural of anecdote is not data. ~ Roger Brinner The combination of some data and an aching desire for an answer does not ensure that a reasonable answer can be extracted from a given body of data. ~ John...
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
That's weird. What is your default shell that Perl invokes with the "system" command. This works fine with bash-2.05b. Reid. On Sun, 2004-09-05 at 10:01, Vladimir Merzliakov wrote: > > x86 FreeBSD: > > * hasn't run with changes yet > > I manually start script. I use this options (+ -verbose now for testing) > >
2017 May 03
2
R 3.4.0 for Ubuntu zesty?
...t voor natuur- en bosonderzoek / Research Institute for Nature and Forest team Biometrie & Kwaliteitszorg / team Biometrics & Quality Assurance Kliniekstraat 25 1070 Anderlecht Belgium To call in the statistician after the experiment is done may be no more than asking him to perform a post-mortem examination: he may be able to say what the experiment died of. ~ Sir Ronald Aylmer Fisher The plural of anecdote is not data. ~ Roger Brinner The combination of some data and an aching desire for an answer does not ensure that a reasonable answer can be extracted from a given body of data. ~ John...
2004 Sep 05
2
[LLVMdev] POST MORTEM: llvm-test changes
On Sun, 2004-09-05 at 13:48, Jeff Cohen wrote: > On Sun, 05 Sep 2004 10:49:44 -0700 > Reid Spencer <reid at x10sys.com> wrote: > > > Jeff, > > > > Actually, that was my fault. I forgot to remove the non-existent > > directories from the configure.ac file. That's done and committed > > now, so the advice is still the same: update configure script