Tag Archives: other

C++ Error: terminating with uncaught exception of type std::out_of_range: vector Abort trap: 6

Toss about for a long time, finally clear the specific reason!
According to the exception prompt, vector is out of bounds, but it has not been located to which vector variable for a long time.
Write the class printf before and after the interrupt position, find the interrupted function, and print inside the function, only to find that the function doesn’t go in at all. It’s strange how you can’t go back in, no other thread, no other place to cause a crash. At this point, I should have thought to check the input of the function earlier. If the input is not correct, the function cannot enter. However, I have never encountered the situation that the input causes the function to not enter, so I did not think to check the input.
The input is a vector type, and the error is due to a problem with the access method.
Vector has a variety of access methods, which can be accessed directly in the way of array, such as VEC variable, VEC [0], or at(), vec.AT (0). There are differences between the two approaches. If veC happens to be empty, accessing the 0th element as an array will not be considered wrong, but the second access using the at method will result in the above error!!

How to generate lib library with keil MDK and use lib Library

reference resources: https://xiaopengzhen.blog.csdn.net/article/details/90036247?utm_ medium= distribute.pc_ relevant.none -task-blog-2%7Edefault%7EBlogCommendFromMachineLearnPai2%7Edefault-4.control&dist_ request_ id=1331647.11602.16183926662894565&depth_ 1-utm_ source= distribute.pc_ relevant.none -task-blog-2%7Edefault%7EBlogCommendFromMachineLearnPai2%7Edefault-4.control

 

1. Organize the source files to be compiled and encapsulate the interface.

2. Add the source file to the MDK project, for example:

3. Setting in MDK: check create library and set the file name of Lib library

4. Compile and view the output file.

5. How to use it will not be repeated.

 

Solution to build error in Vue project (error in static/JS)/vendor.xxxxx.js from UglifyJs)

The project that has been running very well suddenly reported an error in build. The error message is as follows:

ERROR in static/js/vendor.f1c68aa2d5e85847d30e.js from UglifyJs
Unexpected token name «i», expected punc «;» [./node_modules/element-ui/src/utils/merge.js:2,0][static/js/vendor.f1c68aa2d5e85847d30e.js:17064,11]
Build failed with errors.

In uglifyjs’ GitHub issues # 78, we found such a solution: because uglifyjs only supports Es5, and element UI may introduce a part of the writing of ES6, so webpack packaging fails. The final solution given in issue is to replace uglify JS with uglify es of beta version (beta version introduces support for es2015 +). You need to execute the command NPMI - D in the front-end working directory [email protected]

However, after trying, we found that the problem of build error is still unsolved. After searching for the problem, we decided to use bable to parse the element UI. To complete this operation, we only need to modify the build error in the front-end folder/ webpack.base.conf The. JS file can be modified as follows:
before modification

module: {
rules: [
...
{
test: /\.js$/,
loader: 'babel-loader',
include: [resolve('src'), resolve('test')]
},

After modification

 

module: {
rules: [
...
{
test: /\.js$/,
loader: 'babel-loader',//Note that elementUI's source code needs to be parsed using ES6
include: [resolve('src'), resolve('test'),resolve('/node_modules/element-ui/src'),resolve('/node_modules/element-ui/packages')]
},
...

It is equivalent to adding element UI to the package that needs to be parsed by Babel.

After that, execute NPM run build again, and the build is successful.

Failed to load resource: net::ERR_ CACHE_ READ_ Failure solution

When using elasticsearch word segmentation plug-in, kibana is used as the client management, and an error kibana did not load properly. Check the server output for more information

Failed to load resource: Net:: err_ CACHE_ READ_ FAILURE。 Cache read failed.

The reason is that I cleared the browser’s cache before and restarted the computer, which resulted in kibana’s failure to read the cache.

Solution: force the browser cache to refresh again.

Please specify which branch you want to merge with

$git pull

 

$ git pull
warning: no common commits
remote: Counting objects: 5, done.
remote: Compressing objects: 100% (4/4), done.
remote: Total 5 (delta 0), reused 0 (delta 0), pack-reused 0
Unpacking objects: 100% (5/5), done.
From github.com:nonfuxinyang/android-study
 * [new branch]      master     -> origin/master
There is no tracking information for the current branch.
Please specify which branch you want to merge with.
See git-pull(1) for details.

    git pull <remote> <branch>

If you wish to set tracking information for this branch you can do so with:

    git branch --set-upstream-to=origin/<branch> master

Seeing the second tip, we now know a solution. That is to specify the link relationship between the current working directory, working branch, and remote warehouse and branch. ≪ BR & gt;

for example, we set the master branch corresponding to the remote warehouse

git branch — set upstream master origin / Master

so every time we want to push or pull, we just need to enter Git push or git pull.

Before that, we have to specify the remote branch that we want to push or pull.

git push origin master

git pull origin master.

 

 

 

 

Error: java.lang.NumberFormatException : multiple points

Encountered error for java.lang.NumberFormatException : multiple points

The background error is:

java.lang.NumberFormatException: multiple points
	at sun.misc.FloatingDecimal.readJavaFormatString(FloatingDecimal.java:1890)
	at sun.misc.FloatingDecimal.parseDouble(FloatingDecimal.java:110)
	at java.lang.Double.parseDouble(Double.java:538)
	at bus.mdrms.algorithm.indexmodel.exterInterface.StationIndexForecast.initPubertyIndex(StationIndexForecast.java:278)
	at bus.mdrms.algorithm.indexmodel.exterInterface.StationIndexForecast.init(StationIndexForecast.java:51)
	at bus.mdrms.algorithm.indexmodel.exterInterface.StationIndexForecast.calPubertySuitability(StationIndexForecast.java:55)
	at bus.mdrms.algorithm.indexmodel.IndexCalculator.processRequest(IndexCalculator.java:177)
	at com.supermap.mdrms.framework.util.MDRMSUtil.queryMDRMSInfo(MDRMSUtil.java:747)
	at com.supermap.mdrms.modules.mdrms.controller.MdrmsController.queryMDRMSInfo(MdrmsController.java:177)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:498)
	at org.springframework.web.method.support.InvocableHandlerMethod.doInvoke(InvocableHandlerMethod.java:221)
	at org.springframework.web.method.support.InvocableHandlerMethod.invokeForRequest(InvocableHandlerMethod.java:137)
	at org.springframework.web.servlet.mvc.method.annotation.ServletInvocableHandlerMethod.invokeAndHandle(ServletInvocableHandlerMethod.java:111)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.invokeHandlerMethod(RequestMappingHandlerAdapter.java:806)
	at org.springframework.web.servlet.mvc.method.annotation.RequestMappingHandlerAdapter.handleInternal(RequestMappingHandlerAdapter.java:729)
	at org.springframework.web.servlet.mvc.method.AbstractHandlerMethodAdapter.handle(AbstractHandlerMethodAdapter.java:85)
	at org.springframework.web.servlet.DispatcherServlet.doDispatch(DispatcherServlet.java:959)
	at org.springframework.web.servlet.DispatcherServlet.doService(DispatcherServlet.java:893)
	at org.springframework.web.servlet.FrameworkServlet.processRequest(FrameworkServlet.java:970)
	at org.springframework.web.servlet.FrameworkServlet.doPost(FrameworkServlet.java:872)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:650)
	at org.springframework.web.servlet.FrameworkServlet.service(FrameworkServlet.java:846)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:731)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:303)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at com.alibaba.druid.support.http.WebStatFilter.doFilter(WebStatFilter.java:123)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.springframework.web.filter.CharacterEncodingFilter.doFilterInternal(CharacterEncodingFilter.java:85)
	at org.springframework.web.filter.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:107)
	at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:241)
	at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:208)
	at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:218)
	at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:110)
	at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:169)
	at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:103)
	at org.apache.catalina.valves.AccessLogValve.invoke(AccessLogValve.java:962)
	at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:116)
	at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:445)
	at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1115)
	at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:637)
	at org.apache.tomcat.util.net.JIoEndpoint$SocketProcessor.run(JIoEndpoint.java:316)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61)
	at java.lang.Thread.run(Thread.java:748)

The error is multiple points

Same code:
double D_ version = Double.parseDouble ( “1.1.2 “);

Exception in thread "main" java.lang.NumberFormatException: multiple points

It would be the same mistake

double d_ version = Double.parseDouble ( “1..2 “);

It’s also a mistake

 

Mac boot boot the most detailed explanation, so that the automatic start of the program can not escape

##Login items
the program started by the current user of Mac OSX after successful login. The configuration file of the startup items of this category is stored in ~ / library / preferences/ com.apple.loginitems . plist, so only for the current user, you can set it in the following ways:

1. Set under “users and groups” in system preferences, which can be deleted, added, opened and closed;

2. You can modify ~ / library / preferences directly/ com.apple.loginitems . plist configuration file, in which each startup item corresponds to a dictionary, with three values of alias, icon and name, in which name is nsstring type and others are data type. We don’t know how to generate it serially, so we can delete it at present;

3. Add and delete through lssharedfilelistinsertitemurl and lssharedfilelistitemremove method, and related introduction (the registration program starts up)

##Launchdemon
this type of startup items are all started by launchd. Launchd is the key process used to initialize the system environment in Mac OS. It is the first process started in OS environment after the kernel is loaded successfully. In this way, it is very easy to configure the self booting item. Only one plist file is needed. The directory where the plist file exists is

~/Library/LaunchAgents

/Library/LaunchAgents

/System/Library/LaunchAgents

The above three directories are the recommended paths for the system. They are the processes started after login

~/Library/LaunchDaemons

/Library/LaunchDaemons

/System/Library/LaunchDaemons

If it is placed in the above three directories, it will be started as the daemons and the processes started immediately after the system starts

Different directory processes have different permissions and priorities. You can set them in the following ways:

1. Through launchctl load xxx.plist Or launchctl unload xxx.plist Command to add and delete the specified startup items;

2. Directly create, modify and delete plist files under related directories.

The main fields in plist and their meanings

Label is used as a unique identifier in launchd, similar to that every program has an identifier.

User name specifies the user to run the startup item. This item is applicable only when launchd is running as root.

Groupname specifies the group to run the startup item. This item applies only when launchd is running as root.

The key value of keepalive is used to control whether the executable file runs continuously or starts after meeting specific conditions. The default value is false, that is to say, it will not start until the specific conditions are met. When the setting value is true, the executable file will be opened unconditionally and kept in the whole system running cycle.

Runatload identifies that launchd starts the executable file specified by the path immediately after loading the service. The default value is false.

The value program is used to specify the path of the executable file of the process.

Programarguments if program is not specified, it must be specified, including executable files and running parameters.

##3. Startupitems
startupitems, as the name suggests, are programs that run during the system startup. They can be programs that terminate immediately after running (for example, start to empty the wastebasket), or they can be background processes that continue in the system running cycle.

Startupitems are generally stored in the following two paths:

1)/System/Library/StartupItems

2)/Library/StartupItems

Most of the system related startupitems are placed in the path of / system / library / startupitems, and they will be executed prior to the path of / library / startupitems, because the startupitems in the path of the former provide system level basic services, such as crash reporting, core graphics services, system The latter path does not exist by default and needs to be created manually.

Here we take iceberg control tower in / library / startupitems directory as an example.

In short, on Mac OS X, a startupitems includes the following two aspects:

1) Executable program;

2) Plist file containing dependent process relationships( StartupParameters.plist )。

StartupParameters.plist Is a property list that contains the necessary conditions for running an executable program, the main fields in plist, and its meaning

The plist needs to obtain root permission, which includes several aspects:

1)Description;

A simple description of the service is only a description, not the actual process name.

2)Provides;

Specify the services provided by startupitems. As shown in the plist file provides, the background process started by startupitems is named iceberg control tower.

Provides can specify multiple services, which are reflected in the figure as item0, Item1 And so on. There is only item0.

3)Uses;

Specifies the services that need to be opened before startupitems is loaded. The Mac OS X system first attempts to load the service specified in uses, and then loads startupitems. In other words, even if the service specified in uses is not loaded successfully, the system will still load startupitems.

4)OrderPreference;

Specifies the chronological order in which startupitems are executed. The importance of this order comes after uses, which is the order after the specified uses are executed. Possible values include: first, early, none (default), late, last.

5)Messages。

The Executable File

Note: 1) the name of the executable file is the same as that of the folder where it is located, which is the default rule of the system.

2) Root permission is required to operate the executable.

3) The executable is a shell script.

Open the executable file with the same name in the icebergcontroltower file directory to see the specific content of the script

The general executable file includes the following aspects:

1)./etc/ rc.common

A script library provided by apple, which contains the interface of importing parameters for executable files. Here, the library mainly calls runservice.

2)StartService(), StopService(), RestartService()

When the parameters received by the executable file are start, stop or restart, the corresponding functions are executed.

Parameter meaning:

Start: start the service during startup;

Stop: stop the service during shutdown;

Restart: restart the service under specific conditions.

3)RunService “$1”

Executes the service specified by the first parameter passed to the script.

“$1” represents the first parameter passed to the script. For example, if the passed in parameter is start, startservice() is executed.

(some of the contents are quoted in http://blog.csdn.net/abby_ sheen/article/details/7817198

ansoft:Com Engine non-responsive since

Ansoft :Com Engine Non-responsive since 17:23:04, October 18, 2015.If Persisting for Long, Functional Testing kills the Com Engine Process and Restart Analysis.
When this situation occurs in Ansoft simulation, the progress bar is 0 and unchanged. Many methods have been tried on the Internet, but the software crashed and was closed and then opened, which can be simulated normally.

RemoveError: ‘setuptools’ is a dependency of conda and cannot be removed from conda’s operatin

RemoveError: ‘setuptools’ is a dependency of conda and cannot be removed from
conda’s operating environment.

PIP uninstall install setuptools
PIP uninstall install setuptools
c> update conda
conda u>e –force conda

PIP un>all install setuptools
conda install -c anaconda setuptools
conda install -c anaconda setuptools
conda install -c anaconda setuptools
conda install -c anaconda setuptools

The solution to the flash of. Bat file

Recently, when I was doing a project, I found that the.bat file flashed by after I clicked it. I believe that many friends have also encountered the same problem
The following methods:
First, hold down the Shift key in the folder where your.bat file is located and click the right mouse button. Select “Open PowerShell Window here” as shown in the picture

You’ll get a blue command line window and you’ll type.\ the name of your file at the end of the command line and make sure you add a suffix, like mine
.\make_proto.bat

The above methods are effective, of course, there are other methods, friends can choose.