精华内容
下载资源
问答
  • 在ssh命令中可以通过-v选项直接开启调试模式,在连接的过程中将根据设定的调试等级输出对应的信息,这篇文章以确认ssh首次连接的动作为例,说明调试模式的使用方式。

    在这里插入图片描述
    在ssh命令中可以通过-v选项直接开启调试模式,在连接的过程中将根据设定的调试等级输出对应的信息,这篇文章以确认ssh首次连接的动作为例,说明调试模式的使用方式。

    调试模式

    ssh命令中,调试模式有三种,具体说明如下所示:

    类别设定方法使用示例使用说明
    调试模式1-vssh -v 具体命令显示debug1的调试信息
    调试模式2-vvssh -v 具体命令显示debug1和debug2的调试信息
    调试模式3-vvvssh -v 具体命令显示debug1、debug2和debug3的调试信息

    首次连接

    比如在192.168.163.121这台机器上, 使用-v来确认连接的过程:

    输入命令ssh -v 192.168.163.121

    执行之前确认一下.ssh的密钥信息,可以看到有rsa的密钥对

    [root@host121 ssh]# ls $HOME/.ssh
    id_rsa  id_rsa.pub
    [root@host121 ssh]#
    

    执行信息如下所示:

    [root@host121 ssh]# ssh -v 192.168.163.121
    OpenSSH_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: /etc/ssh/ssh_config line 58: Applying options for *
    debug1: Connecting to 192.168.163.121 [192.168.163.121] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /root/.ssh/id_rsa type 1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519 type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519-cert type -1
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_7.4
    debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
    debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
    debug1: Authenticating to 192.168.163.121:22 as 'root'
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: algorithm: curve25519-sha256
    debug1: kex: host key algorithm: ecdsa-sha2-nistp256
    debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
    debug1: Server host key: ecdsa-sha2-nistp256 SHA256:y9ir2Jbc7kNZPhP9h/O9juUZbTmGDo6NZi2IZnLwg0s
    The authenticity of host '192.168.163.121 (192.168.163.121)' can't be established.
    ECDSA key fingerprint is SHA256:y9ir2Jbc7kNZPhP9h/O9juUZbTmGDo6NZi2IZnLwg0s.
    ECDSA key fingerprint is MD5:d5:e7:dc:b3:21:06:5a:e5:c0:f7:a4:60:f7:59:d4:48.
    Are you sure you want to continue connecting (yes/no)?
    

    可以看到开始登录时会确认 /root/.ssh/id_rsa的信息,并返回了存在的信息,在输入known_hosts之前,确认了服务器的密钥指纹信息,并提示用户是否继续

    输入yes继续确认

    输入yes之后,可以看到试图使用密钥方式进行登录的过程,ssh支持密钥方式登录和用户名/密码登录等两种方式,数据传输的安全性都是可以得到保证的,不同在于是否需要输入密码。

    Are you sure you want to continue connecting (yes/no)? yes
    Warning: Permanently added '192.168.163.121' (ECDSA) to the list of known hosts.
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_EXT_INFO received
    debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
    debug1: Next authentication method: gssapi-keyex
    debug1: No valid Key exchange context
    debug1: Next authentication method: gssapi-with-mic
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Next authentication method: publickey
    debug1: Offering RSA public key: /root/.ssh/id_rsa
    debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
    debug1: Trying private key: /root/.ssh/id_dsa
    debug1: Trying private key: /root/.ssh/id_ecdsa
    debug1: Trying private key: /root/.ssh/id_ed25519
    debug1: Next authentication method: password
    root@192.168.163.121's password:
    

    此时在别的终端已经可以确认此时已经生成了know_hosts的信息,这是上一步骤中yes输入之后的结果。

    [root@host121 ~]# ls ~/.ssh
    id_rsa  id_rsa.pub  known_hosts
    [root@host121 ~]# cat ~/.ssh/known_hosts 
    192.168.163.121 ecdsa-sha2-nistp256 AAAAE2VjZHNhLXNoYTItbmlzdHAyNTYAAAAIbmlzdHAyNTYAAABBBEy3w5004yyzNA8dXo1vo67E63tZybV88SiDupDfnHzHCeZ4tHjNqdabc9Fa+Jwwe5uIjcUFb+Ag4HaBjK4982U=
    [root@host121 ~]#
    

    输入密码完成登录

    输入密码之后即可完成登录

    root@192.168.163.121's password: 
    debug1: Authentication succeeded (password).
    Authenticated to 192.168.163.121 ([192.168.163.121]:22).
    debug1: channel 0: new [client-session]
    debug1: Requesting no-more-sessions@openssh.com
    debug1: Entering interactive session.
    debug1: pledge: network
    debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
    debug1: Sending environment.
    debug1: Sending env LANG = en_US.UTF-8
    debug1: Sending env LC_CTYPE = en_US.UTF-8
    Last login: Sat Dec  7 18:48:33 2019 from gateway
    [root@host121 ~]# 
    

    首次之后的连接

    首次之后的连接,不再需要确认know_hosts的信息,使用-v确认结果如下所示

    [root@host121 ~]# ssh -v 192.168.163.121
    OpenSSH_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: /etc/ssh/ssh_config line 58: Applying options for *
    debug1: Connecting to 192.168.163.121 [192.168.163.121] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /root/.ssh/id_rsa type 1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519 type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519-cert type -1
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_7.4
    debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
    debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
    debug1: Authenticating to 192.168.163.121:22 as 'root'
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: algorithm: curve25519-sha256
    debug1: kex: host key algorithm: ecdsa-sha2-nistp256
    debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
    debug1: Server host key: ecdsa-sha2-nistp256 SHA256:y9ir2Jbc7kNZPhP9h/O9juUZbTmGDo6NZi2IZnLwg0s
    debug1: Host '192.168.163.121' is known and matches the ECDSA host key.
    debug1: Found key in /root/.ssh/known_hosts:1
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_EXT_INFO received
    debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
    debug1: Next authentication method: gssapi-keyex
    debug1: No valid Key exchange context
    debug1: Next authentication method: gssapi-with-mic
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Next authentication method: publickey
    debug1: Offering RSA public key: /root/.ssh/id_rsa
    debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
    debug1: Trying private key: /root/.ssh/id_dsa
    debug1: Trying private key: /root/.ssh/id_ecdsa
    debug1: Trying private key: /root/.ssh/id_ed25519
    debug1: Next authentication method: password
    root@192.168.163.121's password: 
    debug1: Authentication succeeded (password).
    Authenticated to 192.168.163.121 ([192.168.163.121]:22).
    debug1: channel 0: new [client-session]
    debug1: Requesting no-more-sessions@openssh.com
    debug1: Entering interactive session.
    debug1: pledge: network
    debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
    debug1: Sending environment.
    debug1: Sending env LANG = en_US.UTF-8
    debug1: Sending env LC_CTYPE = en_US.UTF-8
    Last login: Sat Dec  7 19:46:25 2019 from host121
    [root@host121 ~]# 
    

    密钥登录方式

    ssh连接设定

    SSH在使用中,更多的使用则是使用密钥方式登录,首先使用ssh-copy-id设定登录,本示例中是本机连接本机,但是方式都是相同的。

    [root@host121 ~]# ls ~/.ssh
    id_rsa  id_rsa.pub  known_hosts
    [root@host121 ~]# ssh-copy-id -i 192.168.163.121
    /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/id_rsa.pub"
    /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are already installed
    /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to install the new keys
    root@192.168.163.121's password: 
    
    Number of key(s) added: 1
    
    Now try logging into the machine, with:   "ssh '192.168.163.121'"
    and check to make sure that only the key(s) you wanted were added.
    
    [root@host121 ~]# 
    [root@host121 ~]# ls ~/.ssh
    authorized_keys  id_rsa  id_rsa.pub  known_hosts
    [root@host121 ~]# cat ~/.ssh/authorized_keys 
    ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQCj7f9fLXrbmXCXvdjlKwgJhDZ7VNr8eT++j3elmJq2SmVAPKT2Ows8Xjtrvsik9p7dTCwX6B88VUTTBdAQJCoADTxUIcn847XCkLSz5803d4spR3fVaZl6U+VEvW6fDnTAPUzuWpb2E/lBIVr9x8p1hayZFHtODrKPzyDp1li3fu6F+NR1gVsbiuYIyKH8QJIL1P2QYiyGn0/+qfaJAJ9QvbqmCCnJLhbrfBeFb4e/K+66guctaHc7qPXaeA98kJhKZg5ZqlHY+jC7F4T+/zp/bwophcnk67HakVju++R44zJdGVercZNkHZdMNWfMiwF4Xkt7uT/SEMaLUvWd+3UT root@host121
    [root@host121 ~]# ls -l ~/.ssh
    total 16
    -rw-------. 1 root root  394 Dec  7 19:51 authorized_keys
    -rw-------. 1 root root 1679 Dec  7 16:46 id_rsa
    -rw-r--r--. 1 root root  394 Dec  7 16:46 id_rsa.pub
    -rw-r--r--. 1 root root  177 Dec  7 19:36 known_hosts
    [root@host121 ~]#
    

    当然手动设定也是一样,主要在于authorized_keys文件以及其600的权限需要注意。此文件需要设定在目标机器上。

    连接过程确认

    [root@host121 ~]# ssh -v 192.168.163.121
    OpenSSH_7.4p1, OpenSSL 1.0.2k-fips  26 Jan 2017
    debug1: Reading configuration data /etc/ssh/ssh_config
    debug1: /etc/ssh/ssh_config line 58: Applying options for *
    debug1: Connecting to 192.168.163.121 [192.168.163.121] port 22.
    debug1: Connection established.
    debug1: permanently_set_uid: 0/0
    debug1: identity file /root/.ssh/id_rsa type 1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_rsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_dsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ecdsa-cert type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519 type -1
    debug1: key_load_public: No such file or directory
    debug1: identity file /root/.ssh/id_ed25519-cert type -1
    debug1: Enabling compatibility mode for protocol 2.0
    debug1: Local version string SSH-2.0-OpenSSH_7.4
    debug1: Remote protocol version 2.0, remote software version OpenSSH_7.4
    debug1: match: OpenSSH_7.4 pat OpenSSH* compat 0x04000000
    debug1: Authenticating to 192.168.163.121:22 as 'root'
    debug1: SSH2_MSG_KEXINIT sent
    debug1: SSH2_MSG_KEXINIT received
    debug1: kex: algorithm: curve25519-sha256
    debug1: kex: host key algorithm: ecdsa-sha2-nistp256
    debug1: kex: server->client cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: client->server cipher: chacha20-poly1305@openssh.com MAC: <implicit> compression: none
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: kex: curve25519-sha256 need=64 dh_need=64
    debug1: expecting SSH2_MSG_KEX_ECDH_REPLY
    debug1: Server host key: ecdsa-sha2-nistp256 SHA256:y9ir2Jbc7kNZPhP9h/O9juUZbTmGDo6NZi2IZnLwg0s
    debug1: Host '192.168.163.121' is known and matches the ECDSA host key.
    debug1: Found key in /root/.ssh/known_hosts:1
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_NEWKEYS sent
    debug1: expecting SSH2_MSG_NEWKEYS
    debug1: SSH2_MSG_NEWKEYS received
    debug1: rekey after 134217728 blocks
    debug1: SSH2_MSG_EXT_INFO received
    debug1: kex_input_ext_info: server-sig-algs=<rsa-sha2-256,rsa-sha2-512>
    debug1: SSH2_MSG_SERVICE_ACCEPT received
    debug1: Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password
    debug1: Next authentication method: gssapi-keyex
    debug1: No valid Key exchange context
    debug1: Next authentication method: gssapi-with-mic
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Unspecified GSS failure.  Minor code may provide more information
    No Kerberos credentials available (default cache: KEYRING:persistent:0)
    
    debug1: Next authentication method: publickey
    debug1: Offering RSA public key: /root/.ssh/id_rsa
    debug1: Server accepts key: pkalg rsa-sha2-512 blen 279
    debug1: Authentication succeeded (publickey).
    Authenticated to 192.168.163.121 ([192.168.163.121]:22).
    debug1: channel 0: new [client-session]
    debug1: Requesting no-more-sessions@openssh.com
    debug1: Entering interactive session.
    debug1: pledge: network
    debug1: client_input_global_request: rtype hostkeys-00@openssh.com want_reply 0
    debug1: Sending environment.
    debug1: Sending env LANG = en_US.UTF-8
    debug1: Sending env LC_CTYPE = en_US.UTF-8
    Last login: Sat Dec  7 19:48:37 2019 from host121
    [root@host121 ~]# 
    

    从上述信息中可以看到,由于通过ssh-copy-id进行了ssh密钥设定,所以在证书认证阶段就已经成果,所以没有再有后面的Authentications that can continue: publickey,gssapi-keyex,gssapi-with-mic,password通过密码方式登录的提示信息了流程了。

    展开全文
  • 为Docker和Amazon ECS代理启用调试模式(仅适用于Systemd初始化系统和Amazon Linux) 在与脚本相同的文件夹中创建tar zip文件 用法 以root用户身份运行此项目: # curl -O ...
  • linux shell 启用调试模式的三种方式

    万次阅读 2016-12-16 13:51:22
    linux shell的调试模式在实际应用中有很大作用,其启用方式有多种,总结如下 1. 在调用脚本的时候使用  sh +参数 +脚本名 sh -x shell.script 2.在脚本文件首行实现 #!/bin/bash -x 3. 使用set实现 set -x...

    linux shell的调试模式在实际应用中有很大作用,其启用方式有多种,总结如下

    1. 在调用脚本的时候使用    

     sh  +参数   +脚本名

    sh -x shell.script

    2.在脚本文件首行实现

    #!/bin/bash -x  

    3. 使用set实现

    set -x


    -v  显示所有行,详细模式

    -n  检查语法,不执行命令

    -x shell 跟踪模式,显示所有命令和参数

    展开全文
  • Shell—启用Shell脚本调试模式的方法

    千次阅读 2016-12-26 23:04:00
    本文主要介绍几种启用Shell脚本调试模式的方法 一般情况下,我们会在终端输入一个个命令,来执行操作,但是这种方式对于简单的操作还可以,对于稍微复杂一点的操作就不可行了,因此,可以使用脚本来保存一系列...

    本文主要介绍几种启用Shell脚本调试模式的方法


    一般情况下,我们会在终端输入一个个命令,来执行操作,但是这种方式对于简单的操作还可以,对于稍微复杂一点的操作就不可行了,因此,可以使用脚本来保存一系列命令,供用户多次重复调用执行。


    由于我们并不能保证写的脚本没有bug,因此需要对脚本进行调试,下面我们就来讲讲如何启用脚本调试

    在讲解之前,先介绍写基本知识


    一、脚本及其执行


    一个脚本文件与其他文件的区别主要是它的首行,它包含#!(定义文件类型)和路径名(解释器路径),用于告知系统该文件是一个命令集合,将被指定解释器解释

    脚本首行示例:

    #! /bin/bash          #bash脚本
    
    #!/bin/sh            #sh脚本
    
    执行一个脚本很简单

    $ chmod +x 脚本名     #使其具有可执行权限
    
    $ ./脚本名            #执行脚本或者在其前面指定执行该脚本的解释器

    二、启用Shell脚本调试模式


    先介绍下Shell脚本调试的选项

    -v:详细模式,读取脚本时显示所有行

    -n:语法检查模式,读取命令但是不执行

    -x:跟踪模式,在终端显示所有执行的命令和它们的参数


    启用Shell脚本调试的方法:

    (1)改变Shell脚本的首行

    #!/bin/sh  选项          #根据选项启用不同调试模式,选项可同时使用
    (2)调用Shell调试选项

    $ /bin/sh  选项  ./脚本名            
    (3)使用Shell内置命令set

    该方法比较灵活,可以调试任何一段Shell脚本

    打开调试模式:

    $ set  选项   
    启用调试模式:

    $ set  -选项  
    禁用调试模式:

    $ set  +选项  
    此外,如果我们在Shell脚本的不同部分启用了多个调试模式,可以一次性禁用所有的调试模式:

    $ set  -  

    让我们一起遨游在代码的海洋里!


    展开全文
  • nodejs里的request module是一个进行HTTP通讯非常好用的库,最近查看它的源代码,发现一个有用的调试模式. ![clipboard1]...

    nodejs里的request module是一个进行HTTP通讯非常好用的库,最近查看它的源代码,发现一个有用的调试模式.

    clipboard1

    第134行, 把nodejs当前的环境变量NODE_DEBUG的值写入Request.debug这个标志位。如果标志位为true,则request的很多常用方法调用的时候,都会自动调用debug方法,在控制台上打出有用的辅助信息。

    起初我用set NODE_DEBUG=true, 发现无法成功启用:

    clipboard2

    clipboard3

    仔细看request.js, 发现需要set NODE_DEBUG=request才行:

    clipboard4

    启用调试模式之后的一个例子:

    clipboard5

    能够打印出非常详细的HTTP请求往来,方便程序员排错。
    要获取更多Jerry的原创文章,请关注公众号"汪子熙":

    展开全文
  • Linux 中启用 Shell 脚本的调试模式

    千次阅读 2017-01-15 19:39:06
    在学习脚本或写脚本的初期阶段,我们通常从写小脚本或者几行命令的短脚本开始,调试这样的脚本时我们通常无非就是通过观察它们的输出来确保其正常工作。然而,当我们开始写非常长或上千行命令的高级脚本,例如改变...
  • webconfig中,将改为true
  • 在学习脚本或写脚本的初期阶段,我们通常从写小脚本或者几行命令的短脚本开始,调试这样的脚本时我们通常无非就是通过观察它们的输出来确保其正常工作。 然而,当我们开始写非常长或上千行命令的
  • Android Studio 无法进入debug调试模式

    千次阅读 2018-09-28 20:59:44
    是否开启了调试:关闭了调试,是无法进入debug模式的,启用调试模式,需要在build.gradle配置文件的buildTypes中将debuggable设置为true。 ... buildTypes { sit { ... debuggable true ...
  • Android易于使用,但它为高级用户提供了许多隐藏功能。...你可能已经看到这个名字漂浮在周围,并想知道你是否应该启用它。让我们来看看这种模式的用途以及是否需要它。 什么是USB调试? 简而言之,USB调试允许A...
  • 调试 cmakeHow to enable ... 如何使用cmake启用调试? If we use cmake to build the project, we may want to enabling the debuging mode that cmake invoke gcc with the -g so that we can debug the c...
  • 在受限模式下 vscode 将禁用或限制任务、调试、工作空间设置和扩展,来提高安全性。 点击管理将跳到工作区信任设置: 在这里可以点击 “信任” 退出受限模式 也可以点击 “添加文件夹” 手动添加受信任的文件夹和...
  • asp.net启用调试的作用

    2010-09-28 15:56:00
    其实,这个对话框只是在询问你是否需要调试该页面,一般情况下我还是选择启用的,这样可以获取更多有用的信息,但是必须要指出的是在正式发布该页面的是时候一定不要选择调试模式,不然将会使服务器产生很多不必要的...
  • Python+selenium 自动化-操作已启用的chrome浏览器实例演示,chrome启用调试端口方法。 首先在 chrome 快捷方式的目标后面加上这个参数。 前面是代表调试端口,可以随便用端口,后面指向一个新的文件夹用于存储用户...
  • jetty启用调试功能

    千次阅读 2012-04-01 14:23:28
    开发web程序时,我们都想使修改的代码立即生效,这样非常便于调试。但是我详细查看了jetty的文档似乎没有这样的功能。唯一有个redeploy的功能,个人觉得很鸡肋,我改一点代码,你给我redeploy一下,那我开发岂不是要...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 83,703
精华内容 33,481
关键字:

启用调试模式