Displaying 20 results from an estimated 10917 matches for "invokation".
Did you mean:
invocation
2006 Feb 23
3
rake error
I installed at least one gem since I thought I actually once was able to
run ''rake appdoc'' command since there is an api for my models and the
ez_where plugin that I installed earlier. I wanted to see the api for
pdf-writer which is the gem that I installed most recently.
(no, I haven''t given up the issue of ''looping'' that Kevin and some
others replied
2010 Sep 01
4
NoMethodError: undefined method `force_encoding' for "Conten
Hi everyone!
Im trying to install mechanizer from
http://github.com/tenderlove/mechanize.
I`ve clone the project into /tmp folder. When I do rake inside the
folder /tmp/mechanizer it gives me this error:
mac159180:mechanize renatosis$ rake
(in /private/tmp/mechanize)
/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/bin/ruby -w
-Ilib:bin:test:. -e ''require "rubygems";
2014 Nov 24
1
[LLVMdev] RFC: How to represent SEH (__try / __except) in LLVM IR
Hi Reid,
I've been working on the outlining code and have a prototype that produces what I want for a simple case.
Now I'm thinking about the heuristics for recognizing the various logical pieces for C++ exception handling code and removing them once they’ve been cloned. I've been working from various comments you've made earlier in this thread, and I'd like to run something
2008 Nov 06
8
anyone able to explain logic behind "rake spec" startup (e.g. db:test:prepare => abort_if_pending_migration => invoke environment => etc etc)
anyone able to explain logic behind "rake spec" startup? i.e. the
below steps & why things occur when they do
Macintosh-2:myequity greg$ rake spec --trace
(in /Users/greg/source/myequity)
** Invoke spec (first_time)
** Invoke db:test:prepare (first_time)
** Invoke db:abort_if_pending_migrations (first_time)
** Invoke environment (first_time)
** Execute environment
** Execute
2013 Jul 01
0
Invoker - 0.1.1 release, A gem for managing processes in development environment
Hello Folks,
Invoker is a gem for managing processes in development environment. You can
install the gem via:
~> gem install invoker
And you can clone the code from:
http://github.com/code-mancers/invoker
After Installing gem, you need to create a configuration file:
[rails]
directory = /home/gnufied/god_particle
command = zsh -c ''bundle exec rails s -p
2009 May 22
4
[LLVMdev] invoke semantics
On May 22, 2009, at 10:13 AM, Dale Johannesen wrote:
> Should we document it then? Invokes are confusing enough without
> relying on undocumented behavior:)
It'd be good for someone actually familiar with invoke could comment
on this. Specifically, in the following testcase, the return value of
the invoke is used in the unwind destination, which is not reachable
from the normal
2015 Jan 27
2
[LLVMdev] RFC: Native Windows C++ exception handling
I was thinking about this last night, and I came up with a third alternative which I think looks very promising. It’s basically a re-working of the previous alternative to use the landingpad concept rather than arbitrary fake logic, but it uses a single landing pad for the entire function that mimics the logic of the personality function to dispatch unwinding calls and catch handlers.
I believe
2010 Dec 08
3
[LLVMdev] Inlining and exception handling in LLVM and GCC
Hi Renato,
>>> 1. It eases the future elimination of invoke, or at least, the
>>> treatment of current instruction-level exception (as in Java) in a
>>> cleaner way.
>>
>> I don't see what is cleaner about it, except that it is overall at a higher
>> level of abstraction (see above).
>
> If I got it right, his proposal had the unwind path
2015 Jan 22
5
[LLVMdev] Why does "uwtable" prevent optimizing Invoke -> Call?
Hi,
in r176827 the optimization that turns invokes with empty landing pads
into plain calls was disabled for invocations of function with the
"uwtable" attribute.
But given this code:
struct S { ~S() {}; };
void blackbox();
__attribute__((__noinline__)) void inner() { blackbox(); }
int foo() {
S s;
inner();
return 0;
}
int bar() {
2010 Dec 01
8
[LLVMdev] Alternative exception handling proposal
Here is an alternative proposal to Bill's. It is closer to what we already
have (which can be seen as a good or a bad thing!), and is also closer to
what gcc does. It is more incremental than Bill's and introduces fewer
new concepts.
Executive summary
-----------------
Remove the personality and list of catches out of eh.selector and stick them
directly on invoke instructions.
The
2007 Aug 10
2
jinfo, jboss and ExtendedDTraceProbes
Hi,
I would like to use dtrace to observe some behaviour in my J2EE app
running in JBoss. I start JBoss normally in a 1.6 VM. When I try to
enable set the ExtendedDTraceProbes flag using jinfo, I get a thread
dump in the JBoss console and the message: "Unable to open door: target
process not responding or HotSpot VM not loaded" in the jinfo console.
I have tried this with both
2006 Sep 22
2
foo.expects(:blah).returns(10).then(11) syntax
I recently needed the behavior of my object to change on subsequent
method calls so I added the syntax above.
Here''s the diff of changes I made:
Index: test/mocha/expectation_test.rb
===================================================================
--- test/mocha/expectation_test.rb (revision 854)
+++ test/mocha/expectation_test.rb (working copy)
@@ -95,6 +95,12 @@
2008 Jun 12
4
after :each invoked before formatter?
Hello.
I''m using RSpec with Watir to do some automated tests on IE.
I''ve ran into problem, where I want to make a screenshot of a browser window
when example fails. For that I made custom formatter where in
extra_failure_content i''m invoking screenshot taking methods. Now,
everything works like a charm, as long as I''m not using after :each. I
remember that I
2006 Aug 10
4
error compiling wxruby2
I''m just starting to try out wxruby. I downloaded the CVS and executed
rake. I received the following error -
SWIG Version 1.3.24
Copyright (c) 1995-1998
University of Utah and the Regents of the University of California
Copyright (c) 1998-2004
University of Chicago
Compiled with i386-redhat-linux-g++ [i386-redhat-linux-gnu]
Please see http://www.swig.org for reporting bugs and further
2009 Jul 20
4
[LLVMdev] x86 unwind support[MESSAGE NOT SCANNED]
Hi Mark,
> You are confusing stopping the unwinding at *some* levels or at *all*
> levels.
> Eg.
> invoke
> call
> call
> invoke
> call
> call
> unwind
the dwarf unwinder only stops and runs user code at the invokes.
It does restore registers and so forth at every stack frame.
This is extra work done at unwind time that reduces the cost
2012 Apr 22
2
Cisco AnyConnect on 6.2 32-bit?
Grr.. I'm pulling my hair out trying to get the Cisco AnyConnect client to
work under 6.2 32-bit. Seems like there is always 1 thing preventing my
from using the latest centos release as my sole workstation.
It was actually working on a new install for about half a day. I rebooted
and now it won't connect. If I boot another vm (ubuntu or oel 5.7) the same
client works.
Im using version
2015 Mar 25
2
[LLVMdev] Instruction::mayThrow not handling invoke's?
While improving ADCE, i notice that for
declare i32 @strlen(i8*) readnone
define i32 @test() {
; invoke of pure function should not be deleted!
invoke i32 @strlen( i8* null ) readnone
to label %Cont unwind label %Other ; <i32>:1 [#uses=0]
Cont: ; preds = %0
ret i32 0
Other: ; preds = %0
%exn = landingpad {i8*, i32} personality i32 (...)*
@__gxx_personality_v0
2006 Aug 14
1
rake test:units -> table already exists
Hi!
When I run test:units, rails complains about the tables already being
present. They had to be present so I could run individual unit tests. So
why doesn''t rails just drop the tables if they exist?
Any ideas??
Jeroen
debug oupt below:
>rake test:units --trace
(in ...)
** Invoke test:units (first_time)
** Invoke db:test:prepare (first_time)
** Invoke environment (first_time)
2006 Aug 02
0
rake works but rake test:units fails, strange trace
Hi,
When I run rake, everything works fine but when I run rake test:units
I get an error apparently while it''s trying to create db tables
saying the table already exists. I ran rake with trace to see the
differences. It appears that rake test:units does db:schema:load
twice, maybe that is the problem? Anyone know why this might be?
Output of trace below
Rake
** Invoke default
2010 Dec 01
0
[LLVMdev] Alternative exception handling proposal
On Dec 1, 2010, at 1:37 PM, Duncan Sands wrote:
> Executive summary
> -----------------
>
> Remove the personality and list of catches out of eh.selector and stick them
> directly on invoke instructions.
>
> The invoke instruction
> ----------------------
>
> The invoke instruction is modified by adding extra catch info to it:
>
> <result> = invoke