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

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

    调试模式

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

    类别 设定方法 使用示例 使用说明
    调试模式1 -v ssh -v 具体命令 显示debug1的调试信息
    调试模式2 -vv ssh -v 具体命令 显示debug1和debug2的调试信息
    调试模式3 -vvv ssh -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 跟踪模式,显示所有命令和参数

    展开全文
  • ,如果没有修改则不能进行远程调试,只能在本机进行调试。 Linux系统使用: catalina.sh jpda start windows系统使用: catalina.bat jpda start 这样我们就可以用 idea/ecilpse 里面进行远程debug...

    tomcat7,和 tomcat6 的jpda 不一样,tomcat7已经把jpda配置的属性在catalina.sh/catalina.bat里面已经写好了,我们不需要向tomcat6那样去设置参数。默认的端口为8000端口,我们可以直接调用。

    tomcat8 和 tomcat7 有点小区别,tomcat8 需要在 catalina.sh 文件中设置 

    export JPDA_ADDRESS=8000

     因为该设置默认为 localhost:8000,如果没有修改则不能进行远程调试,只能在本机进行调试。

    Linux系统使用:

    catalina.sh jpda start

    windows系统使用:

    catalina.bat jpda start

    这样我们就可以用 idea/ecilpse 里面进行远程debug了。具体操作就不加以描述。

    转载于:https://www.cnblogs.com/suiyueqiannian/p/5736461.html

    展开全文
  • 使用mprop文件为手机开启调试模式

    一:使用mprop文件为手机开启调试模式(手机需要root)

    将下载好的mprop文件复制到手机 /data/local/tmp文件夹中,选择好手机系统对应的版本

     adb (-s device_serial 有多台设备连接时使用) push "mprop文件在电脑中的路径" /data/local/tmp

    修改mprop文件权限

    adb shell
    
    su
    
    cd /data/local/tmp
    
    chmod 777 mprop 
    
    ./mprop ro.debuggable 1
    
    stop

    二:IDA动态调试

    1. 将IDA目录下的android_server文件复制到手机中的/data/local/tmp目录中
      adb push "C:\Program Files\IDA 7.0\dbgsrv\android_server" /data/local/tmp

       

    2. 进入手机/data/local/tmp目录中,修改文件权限
      adb shell
      su
      cd /data/local/tmp
      chmod 777 android_server

       

    3. 启动android_server(可将android_server文件修改下名字,以防被要调试的程序检测到)

      ./android_server

       

    4. 开启端口转发

      adb forward tcp:pc_port tcp:mobile_port
      
      如有多个设备连接电脑则用
      adb -s serial_no forward tcp:pc_port tcp:mobile_port

       

    5. IDA调试端口设置

      Debugger-->Process Option --> Hostname:localhost Port:port

       

    6. 程序以调试模式启动

      adb shell (-s serial_no) am start -D -n packagename/activityName
      

       

    7. IDA挂接

      Debugger-->Attach to Process

       

    8. cmd命令中打开monitor

    9. 恢复程序运行jdb connect

      jdb -connect com.sun.jdi.SocketAttach:hostname=127.0.0.1,port=8700

       

    展开全文
  • nodejs里的request module是一个进行HTTP通讯非常好用的库,最近查看它的源代码,发现一个有用的调试模式. ![clipboard1]...
  • import logging logging.basicConfig(level=logging.DEBUG, format=' %(asctime)s - %(levelname)s: %(message)s') #format显示格式...#logging.disable(logging.CRITICAL) #调试日志是否显示开关 logging.debug...
  • Shell—启用Shell脚本调试模式的方法

    千次阅读 2016-12-26 23:04:00
    本文主要介绍几种启用Shell脚本调试模式的方法 一般情况下,我们会在终端输入一个个命令,来执行操作,但是这种方式对于简单的操作还可以,对于稍微复杂一点的操作就不可行了,因此,可以使用脚本来保存一系列...
  • 如何在 Linux 中启用 Shell 脚本的调试模式 原创:LCTT https://linux.cn/article-8028-1.html 脚本是存储在一个文件的一系列命令。在终端上输入一个个命令,按顺序执行的方法太弱了,使用脚本,系统中的用户可以在...
  • webconfig中,将改为true
  • Linux 中启用 Shell 脚本的调试模式

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

    千次阅读 2018-09-28 20:59:44
    是否开启了调试:关闭了调试,是无法进入debug模式的,启用调试模式,需要在build.gradle配置文件的buildTypes中将debuggable设置为true。 ... buildTypes { sit { ... debuggable true ...
  • 在学习脚本或写脚本的初期阶段,我们通常从写小脚本或者几行命令的短脚本开始,调试这样的脚本时我们通常无非就是通过观察它们的输出来确保其正常工作。 然而,当我们开始写非常长或上千行命令的高...

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 900
精华内容 360
关键字:

启用调试模式