Idea pop-up window out of memory, modify the parameters and start the no response solution

Today, in the process of development, suddenly idea pop-up prompt out of memory, I changed the parameters on the pop-up, click shutdown, and then I couldn’t start it.

I see that many people on the Internet say that they want to delete the idea folder under the user, but once this is deleted, all the settings of the idea may have to be redone.

Finally, it is found that the changed parameters are in Disk C/user /. Idea (different versions have different folder names)/idea.exe.vmoptions. Just replace this file with idea installation directory/bin/idea.exe.vmoptions.

If you start with idea64.exe, this configuration file is called idea64.exe.vmoptions. This file may be in Disk C/user /. Idea, or Disk C/user /. Idea/config. You can replace it with a file of the same name in the installation directory/bin.

C language problem: 0xc0000005: access conflict occurred when writing to location 0xffffcc.

Recently, I began to learn C language systematically and use scanf in vs2019_ An error occurred when s assigned a value to a string. The error is as follows:
the exception raised at the location of 0x7837ef8c (ucrtbased. DLL) (located in project2.exe): 0xc0000005: an access conflict occurred when writing to the location of 0x01342000
*
after querying some data, we find that this problem should be solved because scanf is encouraged in vs2019 compiler_ S function to prevent the original scanf function array out of bounds（ Using scanf function in vs2019 will report an error (compilation failed)

#define WORD_SIZE 26
char name[WORD_SIZE];
scanf_s("%s",name);

If so, an error will be reported.

If we provide the array name and length, we can compile it.

#define WORD_SIZE 26
char name[WORD_SIZE];
scanf_s("%s",name，WORD_SIZE);

40125,“errmsg“: “invalid appsecret, view more at http://t.cn/RAEkdV

Uniapp development of small programs, access to user information, request back to the background

{
	40125,"errmsg": "invalid appsecret, 
	view more at http://t.cn/RAEkdV
}

WeChat official account platform

After logging in, find the development management

and get appid in the development management

and then you can get the user information and request the background

Qt development, using ODBC interface, query mysql, appear qsqlquery:: Value: not positioned on a valid record

Qt development, using ODBC interface, query mysql, appear qsqlquery:: Value: not positioned on a valid record

Question: in the library management system developed by QT craetor integrated development environment, the newly created database class is used to operate the database. It inherits from QObject and uses the interface provided by ODBC to connect with the database. The database is mysql5.7, When using the following query statement, we report an error:

error information: qsqlquery:: Value: not positioned on a valid record

we query the relevant information:
the solutions we have found
try according to the solutions provided in the article, the problems still exist.

Later, some information was printed in various locations, and it was found that qdebug & lt& lt; condition<& lt; content<& lt;“ The variables condition and content in “on” can be printed normally, but “on” printed out is “?”
when I thought of creating a window before, the window title set in Chinese would be garbled. The solution I found at that time was to add the following code to the. Cpp file of the corresponding class:
?Pragma execution_ character_ set("utf-8")

Solution:
add the code block as shown above to the database.cpp file:

edit test information:

test output successful:

end! Scatter flowers! Record it!

Unable to load file D:: program files (x86) node-v16.4.0-win-x861 because scripts are not allowed to run on this system.

1. Problem description

Because you cannot run scripts on your computer

2. Solutions

(1) Run command window as Administrator

(2) Input command: set executionpolicy remotesignated  
3. Restart the command window to solve the problem

4. Just create it again

【 https://blog.csdn.net/u013513178/article/details/114823445 】

Typeerror in gitbook init: cb.apply is not a function solution

The following error occurred when executing gitbook init:

Find the prompt path, open the polyfills.js file, and find this function

This function is called on lines 65-67

fs.stat = statFix(fs.stat)
fs.fstat = statFix(fs.fstat)
fs.lstat = statFix(fs.lstat)

Comment out the three lines of code to solve the problem

Because of the NPM version problem, you can refer to the following two methods to solve. However, we must pay attention to which polyfills.js has a problem, which is explained in detail in the error prompt.

Recommended reading:
1 https://blog.csdn.net/yq_ forever/article/details/112121742
https://www.cnblogs.com/cyxroot/p/13754475.html

Refused to apply style from ＜URL＞ because its MIME type (‘text/html‘) is not a supported stylesheet

Example: insert lb.html into index.html, and lb.html has a lb.css.

Problem: at this time, index.html may report an error: refuse to apply styles from lb.css. But it’s all normal. No problem.

Attempt failed: Online modifications…/modifications, etc. are invalid here. If we start with index.html and introduce the address of lb.css into lb.html, index.html will not report an error, but lb.html will report an error and so on.

Current method: put lb.css and index.css in the same CSS folder and reference them normally. Index.html and lb.html will not report errors.

How to Solve Fitz module error

To solve Fitz module error
when using Python to process PDF documents, you need to use Fitz module. Because Python   If Fitz is compatible with 3.8, the following error message will appear:
[omit part of the error message]
Runtimeerror:  Directory  ‘ static/’  does not  Exist
the solution is to uninstall Fitz module and install pymupdf module. The following commands are executed:
pip   uninstall   fitz
pip   install   pymupdf

Oops error location method in ARM kernel

The error log information is as follows:

 1 Unable to handle kernel NULL pointer dereference at virtual address 00000014
 2 pgd = c0004000
 3 [00000014] *pgd=00000000
 4 Internal error: Oops: 5 [#1] PREEMPT SMP ARM
 5 Modules linked in:
 6 CPU: 0 PID: 1 Comm: swapper/0 Not tainted 3.10.45 #125
 7 task: dc078000 ti: dc05a000 task.ti: dc05a000
 8 PC is at at24c02_probe+0x78/0xa0
 9 LR is at wake_up_klogd+0x84/0xac
10 pc : [<c03e27c0>]    lr : [<c002d9b0>]    psr: 40000113
11 sp : dc05bdb8  ip : dc05bcc0  fp : dc05bdd4
12 r10: c0a20a80  r9 : 0000009e  r8 : c03e2748
13 r7 : 00000000  r6 : c08ccee4  r5 : c08ccf00  r4 : c075dbbc
14 r3 : 00000000  r2 : 00000001  r1 : 20000193  r0 : 00000020
15 Flags: nZcv  IRQs on  FIQs on  Mode SVC_32  ISA ARM  Segment kernel
16 Control: 10c5387d  Table: 1000404a  DAC: 00000015
17 Process swapper/0 (pid: 1, stack limit = 0xdc05a238)

1) According to the log information, the value of PC is   PC is at at24c02_ probe+0x78/0xa0;

　　at24c02_ Probe: the function indicating the error;

0x78: indicates the offset position of the Error statement in the error function;

0xa0: AT24C02_ The size of probe function

2)   Use arm none Linux gnueabi GCC nm command to find the function AT24C02_ The linear address of probe in the kernel (you can also find it in the system. Map file)

　　arm-none-linux-gnueabi-gcc-nm vmlinux | grep at24c02_ probe

(vmlinux is an uncompressed image file, which is in the compilation folder of the kernel.)

The results are as follows

1 c03e2748 t at24c02_probe

Description AT24C02_ The initial linear address of probe function in kernel is 0xc03e2748;

3) According to the deviation value of 0x78, using the arm none Linux gnueabi objdump command, the disassembly of address c03e2748-c03e27ff is displayed (estimated approximate range)

　　arm-none-linux-gnueabi-objdump -S vmlinux –start-address=0xc03e2748 –stop-address=0xc03e27ff >/tmp/file

Deviation value + starting address of function = 0x78 + 0xc03e2748 = 0xc03e27c0 (it can also be obtained from PC value of log)

The errors found in the file file are as follows:

1  c03e27b8:       e59f0020        ldr     r0, [pc, #32]   ; c03e27e0 <at24c02_probe+0x98>
2  56 c03e27bc:       eb0c86de        bl      c070433c <printk>
3  57     printk("The i2c device id data is %d\n", id->driver_data);
4  58 c03e27c0:       e5971014        ldr     r1, [r7, #20]
5  59 c03e27c4:       e59f0018        ldr     r0, [pc, #24]   ; c03e27e4 <at24c02_probe+0x9c>
6  60 c03e27c8:       eb0c86db        bl      c070433c <printk>

We can see that the wrong statement is: printk (“the I2C device ID data is% D/N”, ID – & gt; driver_ data);

Another method:  
You can directly obtain the following information through the addr2line command:

Execute the following command under the compiled source code folder to show which line of code of that function has problems,  
    arm-none-linux-gnueabi-addr2line -e vmlinux   c03e27c0

/opt/Sourcery_CodeBench_for_ARM_Embedded/bin/arm-none-linux-gnueabi-addr2line -e vmlinux c03e27c0

Note: please make sure that cross_ Compile is compiled with the same prefix as you, such as arm none Linux gnueabi – above. You must compile with this prefix, otherwise the calculated line number may deviate greatly.