search for: line_numb

...dleAbort(int Sig) Line 411 C++ Symbols loaded. ucrtbased.dll!raise(int signum) Line 541 C++ Symbols loaded. ucrtbased.dll!abort() Line 64 C++ Symbols loaded. ucrtbased.dll!common_assert_to_stderr_direct(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number) Line 161 C++ Symbols loaded. ucrtbased.dll!common_assert_to_stderr<wchar_t>(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number) Line 175 C++ Symbols loaded. ucrtbased.dll!common_assert<wchar_t>(const wchar_t * const expression,...

This one triggers an assertion in calculateSEHStateNumbers due to weird catchpad instruction in @_island_debug_invoke and many other functions. The code expects either pointer to a filter function or null in first operand, while you're passing pointer to structure: catchpad within %80 [{i8*, i8*}* anon..., ...] ________________________________________ От: Carlo Kok <ck at

...Symbols loaded. ucrtbased.dll!raise(int signum) Line 541 C++ Symbols loaded. ucrtbased.dll!abort() Line 64 C++ Symbols loaded. ucrtbased.dll!common_assert_to_stderr_direct(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number) Line 161 C++ Symbols loaded. ucrtbased.dll!common_assert_to_stderr<wchar_t>(const wchar_t * const expression, const wchar_t * const file_name, const unsigned int line_number) Line 175 C++ Symbols loaded. ucrtbased.dll!common_assert<wchar_t>(const wchar_t *...

Op 16-3-2018 om 20:16 schreef Evgeny Leviant: > Hello Carlo, > > I tried your reproducer and faced different problem from one you described > (I'm using MacOS Sierra and lld built from trunk on Mar, 15). The crash happens > when SelectionDAGBuilder::lowerInvokable tries to access EH info of this function: > >

I a using delayed_job, and I am raising an exception this way : config/initializers/custom_exceptions.rb class RemoteLockerException < StandardError; end class RemoteLockerDenied < StandardError; end lib/instruction_request_job.rb class InstructionRequestJob < Struct.new(:style, :request_id) def perform .... > connector =

...matter to get the path of the file a passing spec belongs to. Following rspec on github I saw that implementation_backtrace is now deprecated and replaced by example.backtrace. Sadly it always returns nil for passed specs. So I had a look at the source and found that backtrace only gets assigned if line_number was set. Can anybody tell me why this was changed to only work with line_number set and if there is another way to get the file a spec belongs to. Thanks for your help! lg // andreas

...ion - should accept uploaded files and save them into the `files` directory (FAILED - 1) 1) ''Application should accept uploaded files and save them into the `files` directory'' FAILED expected [] to include "files/test_file.png" <path_to_app>/controller.spec.rb:<line_number>:in `block (2 levels) in <top (required)>'' Finished in 0.132799038 seconds 1 example, 1 failure What I do wrong? Thanks. Debian GNU/Linux 5.0.4; Ruby 1.9.2; Sinatra 0.9.6; RSpec 1.3.0; Rack-Test 0.5.3. -- Posted via http://www.ruby-forum.com/.

...object), then, I can instrument some code at the IR level to dump V. As long as I maintain V at this pass stage, I should be able to dump the loop trip count. This is true, isn't it? Basically, what I am going to do is to add a function call before the loop body, such as: dumpInfo(FILE_NAME, LINE_NUMBER, VALUE_TYPE, Value) ... for (int i=0; i<num; i++) of course, this may have some side effects. If the trip count is a function call, and I need to rewrite the loop header to avoid calling the function twice. For example, if the loop header is: for (int i=0; i<foo(a,b,c); i++) then I shoul...

...some code at the IR level to > dump V. As long as I maintain V at this pass stage, I should be able > to dump the loop trip count. This is true, isn't it? > > Basically, what I am going to do is to add a function call before the > loop body, such as: > > dumpInfo(FILE_NAME, LINE_NUMBER, VALUE_TYPE, Value) > ... > for (int i=0; i<num; i++) > > of course, this may have some side effects. If the trip count is a > function call, and I need to rewrite the loop header to avoid calling > the function twice. For example, if the loop header is: > > for (int i=...

...t;pending_count":0 }, "examples": [ { "status": "passed", "description": "should == \"an object\"", "full_description": "something in context ", "line_number": 4, "file_path": "./spec/test_spec.rb" } ] } Note that the full_description is missing the matcher documentation. And with ci_reporter 1.8.4, this comes out as a sorry hash indeed, because _only_ the full descriptions are reported to CI. Here'...

...>>> verifyscript = [] >>>>>>> - keywords = ['RUN:', 'VERIFY:'] >>>>>>> + metricscripts = {} >>>>>>> + keywords = ['RUN:', 'VERIFY:', 'METRIC:'] >>>>>>> for line_number, command_type, ln in \ >>>>>>> parseIntegratedTestScriptCommands(filename, >>>>>>> keywords): >>>>>>> if command_type == 'RUN': >>>>>>> _parseShellCommand(runscript, ln) &gt...

...rifyscript = [] >>>>>>>> - keywords = ['RUN:', 'VERIFY:'] >>>>>>>> + metricscripts = {} >>>>>>>> + keywords = ['RUN:', 'VERIFY:', 'METRIC:'] >>>>>>>> for line_number, command_type, ln in \ >>>>>>>> parseIntegratedTestScriptCommands(filename, >>>>>>>> keywords): >>>>>>>> if command_type == 'RUN': >>>>>>>> _parseShellCommand(ru...

...>>>>>>>>> - keywords = ['RUN:', 'VERIFY:'] >>>>>>>>> + metricscripts = {} >>>>>>>>> + keywords = ['RUN:', 'VERIFY:', 'METRIC:'] >>>>>>>>> for line_number, command_type, ln in \ >>>>>>>>> parseIntegratedTestScriptCommands(filename, >>>>>>>>> keywords): >>>>>>>>> if command_type == 'RUN': >>>>>>>>> _pars...

I?d like to solicit some advice on a debugging problem I have in the quantreg package. Kurt and Brian have reported to me that on Debian machines with gfortran 9 library(quantreg) f = summary(rq(foodexp ~ income, data = engel, tau = 1:4/5)) plot(f) fails because summary() produces bogus estimates of the coefficient bounds. This example has been around in my R package from the earliest days of R,

This is v3 of my disk series. What were previously patches 01-06 have been applied. These are the tested and updated remainder, addressing the previous comments. 1 Preparatory work. 2-4 The new parser and its documentation. 5-6 Replace old parsers with calls to the new one. 7-8 Two features, one of them essential. 9 Basic test suite for disk string parsing, as adhoc script.