add backtrace to your program

最新推荐文章于 2019-11-25 20:29:08 发布
转载 最新推荐文章于 2019-11-25 20:29:08 发布 · 921 阅读 · 0

本文介绍如何利用GDB调试工具中的回溯功能(bt)来查看程序崩溃时的调用堆栈，帮助开发者快速定位问题所在。
WGS_LV
关注
arm平台的调用栈回溯(backtrace)
llljjlj的博客
04-26 4570
title: arm平台的调用栈回溯(backtrace) date: 2018-09-19 16:07:47 tags: --- 介绍 arm平台的调用栈与x86平台的调用栈大致相同，稍微有些区别，主要在于栈帧的压栈内容和传参方式不同。在arm平台的不同程序，采用的编译选项不同，程序运行期间的栈帧也会不同。有些工具在对arm的调用栈回溯时，可能会遇到无法回溯的情况。例如gdb在使用bt查看core dump文件调用栈时，有时会出现Backtrace stoped的情况,有可能就是栈空间的压栈顺序导致的
Failed to load E:\SDK\android-sdk-windows\build-tools\27.0.2\lib\dx.jar如何简单解决
热门推荐
lz_1990的专栏
12-19 2万+
Eclipse遇到如下错误： Failed to load E:\SDK\android-sdk-windows\build-tools\27.0.2\lib\dx.jar 原因： eclipse自动使用最高版本的SDK，ADT比SDK版本低导致 解决办法： 1、用SDK Manager.exe下载低版本的build-tools，如25.0.2 2、add this
backtrace函数的使用
落尘纷扰的专栏
03-07 1万+
backtrace()是glibc（>=2.1）提供的函数，用于跟踪函数的调用关系。 以下对backtrace()函数的说明以及实例，都来自其man page。 函数定义        #include        int backtrace(void **buffer, int size);        char **backtrace_symbols(void
应用程序调试-signal和backtrace
vertor11的博客
04-10 2325
优秀博客： https://blog.youkuaiyun.com/skdkjzz/article/details/46046271 https://blog.youkuaiyun.com/littlefang/article/details/42295803 http://blog.chinaunix.net/uid-24774106-id-3457205.html 一.利用backtrace，栈信息找bug ...
解决Failed to load D:\Android-Studio\sdk\build-tools\26.0.1\lib\dx.jar
weimiannihao的博客
09-18 1万+
问题：升级了sdk之后运行出错，Failed to load D:\Android-Studio\sdk\build-tools\26.0.1\lib\dx.jar Unable to build: the file dx.jar was not loaded from the SDK folder 网上找了半天照着解决，结果都不成功，最后硬着头皮看英文最后解决了，记录一下。
善用backtrace解决大问题
龙图腾的博客
01-22 1790
一．用途： 主要用于程序异常退出时寻找错误原因 二．功能： 回溯堆栈，简单的说就是可以列出当前函数调用关系 三．原理： 1．  通过对当前堆栈的分析，找到其上层函数在栈中的帧地址，再分析上层函数的堆栈，再找再上层的帧地址……一直找到最顶层为止，帧地址指的是一块：在栈上存放局部变量，上层返回地址，及寄存器值的空间。 2．  由于不同处理器堆栈方式不同，此功能的具体实现是编
请告诉我具体的实验步骤： Lab: system calls In the last lab you used system calls to write a few utilities. In this lab you will add some new system calls to xv6, which will help you understand how they work and will expose you to some of the internals of the xv6 kernel. You will add more system calls in later labs. Before you start coding, read Chapter 2 of the xv6 book, and Sections 4.3 and 4.4 of Chapter 4, and related source files: • The user-space "stubs" that route system calls into the kernel are in user/usys.S, which is generated by user/usys.pl when you run make. Declarations are in user/user.h • The kernel-space code that routes a system call to the kernel function that implements it is in kernel/syscall.c and kernel/syscall.h. • Process-related code is kernel/proc.h and kernel/proc.c. To start the lab, switch to the syscall branch: $ git fetch $ git checkout syscall $ make clean If you run make grade you will see that the grading script cannot exec trace and sysinfotest. Your job is to add the necessary system calls and stubs to make them work. Using gdb (easy) In many cases, print statements will be sufficient to debug your kernel, but sometimes being able to single step through some assembly code or inspecting the variables on the stack is helpful. To learn more about how to run GDB and the common issues that can arise when using GDB, check out this page. To help you become familiar with gdb, run and then fire up gdb in another window (see the gdb bullet on the guidance page). Once you have two windows open, type in the gdb window: make qemu-gdb (gdb) b syscall Breakpoint 1 at 0x80002142: file kernel/syscall.c, line 243. (gdb) c Continuing. [Switching to Thread 1.2] Thread 2 hit Breakpoint 1, syscall () at kernel/syscall.c:243 243 { (gdb) layout src (gdb) backtrace The layout command splits the window in two, showing where gdb is in the source code. The backtrace prints out the stack backtrace. See Using the GNU Debugger for helpful GDB commands. Answer the following questions in answers-syscall.txt. Looking at the backtrace output, which function called syscall? Type a few times to step past struct proc *p = myproc(); Once past this statement, type , which prints the current process's proc struct (see kernel/proc.h>) in hex. np /x *p What is the value of p->trapframe->a7 and what does that value represent? (Hint: look user/initcode.S, the first user program xv6 starts.) The processor is running in kernel mode, and we can print privileged registers such as sstatus (see RISC-V privileged instructions for a description): (gdb) p /x $sstatus What was the previous mode that the CPU was in? In the subsequent part of this lab (or in following labs), it may happen that you make a programming error that causes the xv6 kernel to panic. For example, replace the statement num = p->trapframe->a7; with num = * (int *) 0; at the beginning of syscall, run , and you will see something similar to: make qemu xv6 kernel is booting hart 2 starting hart 1 starting scause 0x000000000000000d sepc=0x000000008000215a stval=0x0000000000000000 panic: kerneltrap Quit out of qemu. To track down the source of a kernel page-fault panic, search for the sepc value printed for the panic you just saw in the file kernel/kernel.asm, which contains the assembly for the compiled kernel. Write down the assembly instruction the kernel is panicing at. Which register corresponds to the variable num? To inspect the state of the processor and the kernel at the faulting instruction, fire up gdb, and set a breakpoint at the faulting epc, like this: (gdb) b *0x000000008000215a Breakpoint 1 at 0x8000215a: file kernel/syscall.c, line 247. (gdb) layout asm (gdb) c Continuing. [Switching to Thread 1.3] Thread 3 hit Breakpoint 1, syscall () at kernel/syscall.c:247 Confirm that the faulting assembly instruction is the same as the one you found above. Why does the kernel crash? Hint: look at figure 3-3 in the text; is address 0 mapped in the kernel address space? Is that confirmed by the value in scause above? (See description of scause in RISC-V privileged instructions) Note that scause was printed by the kernel panic above, but often you need to look at additional info to track down the problem that caused the panic. For example, to find out which user process was running when the kernel paniced, you can print out the process's name: (gdb) p p->name What is the name of the binary that was running when the kernel paniced? What is its process id (pid)? This concludes a brief introduction to tracking down bugs with gdb; it is worth your time to revisit Using the GNU Debugger when tracking down kernel bugs. The guidance page also has some other other useful debugging tips.
11-16
根据用户需求，我需要提供xv6系统调用实验的具体步骤，包括添加新系统调用、使用GDB调试、解答相关问题以及追踪内核崩溃问题。下面我将分步骤详细说明。 ### 1....在xv6中添加新系统调用需要修改以下文件： ...
root@code:/etc/samba# cat smb.conf # # Sample configuration file for the Samba suite for Debian GNU/Linux. # # # This is the main Samba configuration file. You should read the # smb.conf(5) manual page in order to understand the options listed # here. Samba has a huge number of configurable options most of which # are not shown in this example # # Some options that are often worth tuning have been included as # commented-out examples in this file. # - When such options are commented with ";", the proposed setting # differs from the default Samba behaviour # - When commented with "#", the proposed setting is the default # behaviour of Samba but the option is considered important # enough to be mentioned here # # NOTE: Whenever you modify this file you should run the command # "testparm" to check that you have not made any basic syntactic # errors. #======================= Global Settings ======================= [global] ## Browsing/Identification ### # Change this to the workgroup/NT-domain name your Samba server will part of workgroup = WORKGROUP # server string is the equivalent of the NT Description field server string = %h server (Samba, Ubuntu) #### Networking #### # The specific set of interfaces / networks to bind to # This can be either the interface name or an IP address/netmask; # interface names are normally preferred ; interfaces = 127.0.0.0/8 eth0 # Only bind to the named interfaces and/or networks; you must use the # 'interfaces' option above to use this. # It is recommended that you enable this feature if your Samba machine is # not protected by a firewall or is a firewall itself. However, this # option cannot handle dynamic or non-broadcast interfaces correctly. ; bind interfaces only = yes #### Debugging/Accounting #### # This tells Samba to use a separate log file for each machine # that connects log file = /var/log/samba/log.%m # Cap the size of the individual log files (in KiB). max log size = 1000 # We want Samba to only log to /var/log/samba/log.{smbd,nmbd}. # Append syslog@1 if you want important messages to be sent to syslog too. logging = file # Do something sensible when Samba crashes: mail the admin a backtrace panic action = /usr/share/samba/panic-action %d ####### Authentication ####### # Server role. Defines in which mode Samba will operate. Possible # values are "standalone server", "member server", "classic primary # domain controller", "classic backup domain controller", "active # directory domain controller". # # Most people will want "standalone server" or "member server". # Running as "active directory domain controller" will require first # running "samba-tool domain provision" to wipe databases and create a # new domain. server role = standalone server obey pam restrictions = yes # This boolean parameter controls whether Samba attempts to sync the Unix # password with the SMB password when the encrypted SMB password in the # passdb is changed. unix password sync = yes # For Unix password sync to work on a Debian GNU/Linux system, the following # parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for # sending the correct chat script for the passwd program in Debian Sarge). passwd program = /usr/bin/passwd %u passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* . # This boolean controls whether PAM will be used for password changes # when requested by an SMB client instead of the program listed in # 'passwd program'. The default is 'no'. pam password change = yes # This option controls how unsuccessful authentication attempts are mapped # to anonymous connections map to guest = bad user ########## Domains ########### # # The following settings only takes effect if 'server role = primary # classic domain controller', 'server role = backup domain controller' # or 'domain logons' is set # # It specifies the location of the user's # profile directory from the client point of view) The following # required a [profiles] share to be setup on the samba server (see # below) ; logon path = \\%N\profiles\%U # Another common choice is storing the profile in the user's home directory # (this is Samba's default) # logon path = \\%N\%U\profile # The following setting only takes effect if 'domain logons' is set # It specifies the location of a user's home directory (from the client # point of view) ; logon drive = H: # logon home = \\%N\%U # The following setting only takes effect if 'domain logons' is set # It specifies the script to run during logon. The script must be stored # in the [netlogon] share # NOTE: Must be store in 'DOS' file format convention ; logon script = logon.cmd # This allows Unix users to be created on the domain controller via the SAMR # RPC pipe. The example command creates a user account with a disabled Unix # password; please adapt to your needs ; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u # This allows machine accounts to be created on the domain controller via the # SAMR RPC pipe. # The following assumes a "machines" group exists on the system ; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u # This allows Unix groups to be created on the domain controller via the SAMR # RPC pipe. ; add group script = /usr/sbin/addgroup --force-badname %g ############ Misc ############ # Using the following line enables you to customise your configuration # on a per machine basis. The %m gets replaced with the netbios name # of the machine that is connecting ; include = /home/samba/etc/smb.conf.%m # Some defaults for winbind (make sure you're not using the ranges # for something else.) ; idmap config * : backend = tdb ; idmap config * : range = 3000-7999 ; idmap config YOURDOMAINHERE : backend = tdb ; idmap config YOURDOMAINHERE : range = 100000-999999 ; template shell = /bin/bash # Setup usershare options to enable non-root users to share folders # with the net usershare command. # Maximum number of usershare. 0 means that usershare is disabled. # usershare max shares = 100 # Allow users who've been granted usershare privileges to create # public shares, not just authenticated ones usershare allow guests = yes #======================= Share Definitions ======================= # Un-comment the following (and tweak the other settings below to suit) # to enable the default home directory shares. This will share each # user's home directory as \\server\username ;[homes] ; comment = Home Directories ; browseable = no # By default, the home directories are exported read-only. Change the # next parameter to 'no' if you want to be able to write to them. ; read only = yes # File creation mask is set to 0700 for security reasons. If you want to # create files with group=rw permissions, set next parameter to 0775. ; create mask = 0700 # Directory creation mask is set to 0700 for security reasons. If you want to # create dirs. with group=rw permissions, set next parameter to 0775. ; directory mask = 0700 # By default, \\server\username shares can be connected to by anyone # with access to the samba server. # Un-comment the following parameter to make sure that only "username" # can connect to \\server\username # This might need tweaking when using external authentication schemes ; valid users = %S # Un-comment the following and create the netlogon directory for Domain Logons # (you need to configure Samba to act as a domain controller too.) ;[netlogon] ; comment = Network Logon Service ; path = /home/samba/netlogon ; guest ok = yes ; read only = yes # Un-comment the following and create the profiles directory to store # users profiles (see the "logon path" option above) # (you need to configure Samba to act as a domain controller too.) # The path below should be writable by all users so that their # profile directory may be created the first time they log on ;[profiles] ; comment = Users profiles ; path = /home/samba/profiles ; guest ok = no ; browseable = no ; create mask = 0600 ; directory mask = 0700 [printers] comment = All Printers browseable = no path = /var/spool/samba printable = yes guest ok = no read only = yes create mask = 0700 [Share] path = /root/HJ/data available = yes valid users = hjyf read only = yes browsable = yes # Windows clients look for this share name as a source of downloadable # printer drivers [print$] comment = Printer Drivers path = /var/lib/samba/printers browseable = yes read only = yes guest ok = no # Uncomment to allow remote administration of Windows print drivers. # You may need to replace 'lpadmin' with the name of the group your # admin users are members of. # Please note that you also need to set appropriate Unix permissions # to the drivers directory for these users to have write rights in it ; write list = root, @lpadmin
09-30
我们被要求分析用户提供的Samba配置文件片段，并给出可能的优化或问题解决方法。 用户提供的配置片段是： #log.smbd和log.nmbd日志路径 log file = /var/log/samba/log.%m #日志容量（单位为KB） max log size = ...
Failed to load C:\SDK\android-sdk-windows\build-tools\29.0.2\lib\dx.jar
云卷云舒i的博客
11-25 3685
Eclipse遇到如下错误： Failed to load C:\SDK\android-sdk-windows\build-tools\27.0.2\lib\dx.jar 原因： 国内现在可以访问的ADT版本是23.0.6，Google已经不再更新ADT了，这就会导致现有的ADT版本比SDK版本低。 所以引用dx.jar时会失败。 解决办法： 将低版本的dx.jar文件替...
Failed to load D:\SDK\Android_sdk\build-tools\29.0.2\lib\dx.jar-----简单解决鼠标点点点
蚂蝗征途
11-02 5096
每次遇到错误在网上搜索总是得到很多奇怪的答案，这可能是因为大家使用的环境，软件版本都不一样的原因吧，希望我的记录能帮助到大家，欢迎转载，备注原创。 Eclipse遇到如下错误： Failed to load D:\SDK\Android_sdk\build-tools\29.0.2\lib\dx.jar 原因： eclipse自动使用最高版本的SDK的工具，由于ADT已经停止更新，导致ADT版本...
Eclipse出现Failed to load C:\SDK\android-sdk-windows\build-tools\27.0.2\lib\dx.jar问题
AYNGPENG的博客
05-29 1511
转载自https://blog.youkuaiyun.com/jinyan1111/article/details/79119822把高版本的bulid-tools删除即可
Failed to load D:\Andorid\AndroidSDK\android-sdk-windows\build-tools\29.0.0-preview\lib\dx.jarUnknow
白猫黑猫
06-04 3973
[2019-06-04 13:24:54 - Dex Loader] Failed to load D:\Andorid\AndroidSDK\android-sdk-windows\build-tools\29.0.0-preview\lib\dx.jar [2019-06-04 13:24:54 - HelloWorld] Unknown error: Unable to build: the...
基于SSM与Vue架构的病人跟踪治疗信息管理系统设计与实现（含源码及文档）
12-22
基于SSM架构与Vue技术构建的病人治疗追踪管理系统，采用Java编程语言实现业务逻辑，并以MySQL数据库作为数据存储支持。该系统主要包含三个用户角色：管理员、病人及普通访客。 管理员具备的功能模块包括：主界面、个人设置、病人档案管理、病例信息采集、预约安排、医生信息维护、核酸检测报告上传管理、行动轨迹记录管理、疾病分类配置、病人治疗进度跟踪、留言板处理以及系统参数管理。病人用户可操作：主界面、个人设置、病例信息查看、预约申请、医生查询、核酸检测报告上传、行动轨迹上报、个人治疗状态查询。访客端提供：首页浏览、医生信息展示、医疗资讯发布、留言反馈提交、个人中心、后台入口及在线咨询服务。 系统设计注重代码结构的清晰性与可维护性，强调功能实用性和界面简洁度，同时保持较强的扩展适应能力，便于后续功能升级与日常运维。 项目已通过实际运行测试，开发环境配置如下： - 编程语言：Java - 开发框架：Spring Boot - Java开发工具包：JDK 1.8 - 应用服务器：Tomcat 7 - 数据库系统：MySQL 5.7 - 数据库管理工具：Navicat 12 - 集成开发环境：Eclipse或IntelliJ IDEA - 项目构建工具：Maven 3.3.9。 资源来源于网络分享，仅用于学习交流使用，请勿用于商业，如有侵权请联系我删除！
电力系统单机无穷大电力系统短路故障暂态稳定Simulink仿真（带说明文档）
最新发布
12-22
【电力系统】单机无穷大电力系统短路故障暂态稳定Simulink仿真（带说明文档）内容概要：本文档围绕“单机无穷大电力系统短路故障暂态稳定Simulink仿真”展开，提供了完整的仿真模型与说明文档，重点研究电力系统在发生短路故障后的暂态稳定性问题。通过Simulink搭建单机无穷大系统模型，模拟不同类型的短路故障（如三相短路），分析系统在故障期间及切除后的动态响应，包括发电机转子角度、转速、电压和功率等关键参数的变化，进而评估系统的暂态稳定能力。该仿真有助于理解电力系统稳定性机理，掌握暂态过程分析方法。; 适合人群：电气工程及相关专业的本科生、研究生，以及从事电力系统分析、运行与控制工作的科研人员和工程师。; 使用场景及目标：①学习电力系统暂态稳定的基本概念与分析方法；②掌握利用Simulink进行电力系统建模与仿真的技能；③研究短路故障对系统稳定性的影响及提高稳定性的措施（如故障清除时间优化）；④辅助课程设计、毕业设计或科研项目中的系统仿真验证。; 阅读建议：建议结合电力系统稳定性理论知识进行学习，先理解仿真模型各模块的功能与参数设置，再运行仿真并仔细分析输出结果，尝试改变故障类型或系统参数以观察其对稳定性的影响，从而深化对暂态稳定问题的理解。
这是一个基于Prisma和SQLite数据库构建的现代化轻量级且开箱即用的个人作品集展示平台后端服务系统_该项目核心功能包括用户认证授权作品数据模型管理文件上传存储以及提供标.zip
12-22
这是一个基于Prisma和SQLite数据库构建的现代化轻量级且开箱即用的个人作品集展示平台后端服务系统_该项目核心功能包括用户认证授权作品数据模型管理文件上传存储以及提供标.zip
基于PSO算法优化支持向量机参数的MATLAB仿真源码：SVM与PSO-SVM性能对比
12-22
本研究聚焦于运用MATLAB平台，将支持向量机（SVM）应用于数据预测任务，并引入粒子群优化（PSO）算法对模型的关键参数进行自动调优。该研究属于机器学习领域的典型实践，其核心在于利用SVM构建分类模型，同时借助PSO的全局搜索能力，高效确定SVM的最优超参数配置，从而显著增强模型的整体预测效能。 支持向量机作为一种经典的监督学习方法，其基本原理是通过在高维特征空间中构造一个具有最大间隔的决策边界，以实现对样本数据的分类或回归分析。该算法擅长处理小规模样本集、非线性关系以及高维度特征识别问题，其有效性源于通过核函数将原始数据映射至更高维的空间，使得原本复杂的分类问题变得线性可分。 粒子群优化算法是一种模拟鸟群社会行为的群体智能优化技术。在该算法框架下，每个潜在解被视作一个“粒子”，粒子群在解空间中协同搜索，通过不断迭代更新自身速度与位置，并参考个体历史最优解和群体全局最优解的信息，逐步逼近问题的最优解。在本应用中，PSO被专门用于搜寻SVM中影响模型性能的两个关键参数——正则化参数C与核函数参数γ的最优组合。 项目所提供的实现代码涵盖了从数据加载、预处理（如标准化处理）、基础SVM模型构建到PSO优化流程的完整步骤。优化过程会针对不同的核函数（例如线性核、多项式核及径向基函数核等）进行参数寻优，并系统评估优化前后模型性能的差异。性能对比通常基于准确率、精确率、召回率及F1分数等多项分类指标展开，从而定量验证PSO算法在提升SVM模型分类能力方面的实际效果。 本研究通过一个具体的MATLAB实现案例，旨在演示如何将全局优化算法与机器学习模型相结合，以解决模型参数选择这一关键问题。通过此实践，研究者不仅能够深入理解SVM的工作原理，还能掌握利用智能优化技术提升模型泛化性能的有效方法，这对于机器学习在实际问题中的应用具有重要的参考价值。 资源来源于网络分享，仅用于学习交流使用，请勿用于商业，如有侵权请联系我删除！
jank_record_1766403318764055404.pb
12-22
jank_record_1766403318764055404.pb
分层模糊系统：梯度下降与递推最小二乘法联合辨识研究（Matlab代码实现）
12-22
分层模糊系统：梯度下降与递推最小二乘法联合辨识研究（Matlab代码实现）内容概要：本文围绕“分层模糊系统：梯度下降与递推最小二乘法联合辨识研究”展开，介绍了基于Matlab代码实现的分层模糊系统参数辨识方法。通过结合梯度下降法和递推最小二乘法，实现对系统结构和参数的高效联合辨识，提升模型精度与收敛速度。文中详细阐述了算法原理、实现步骤及仿真验证过程，展示了该方法在非线性系统建模与辨识中的有效性，适用于复杂动态系统的建模与控制研究。; 适合人群：具备一定Matlab编程基础和系统辨识理论背景的研究生、科研人员及自动化、控制工程等相关领域的技术人员。; 使用场景及目标：①应用于非线性动态系统的建模与参数辨识；②用于提高模糊系统训练效率与预测精度；③支持科研复现、算法优化及工程实际中的系统辨识任务； 阅读建议：建议读者结合提供的Matlab代码进行实践操作，深入理解两种优化算法的融合机制，并尝试在不同数据集或应用场景中进行迁移与改进，以掌握其核心思想与实现技巧。
AL-SHADE-SVM分类预测：基于变体差分进化算法的SVM参数优化研究（Matlab代码实现
12-22
AL-SHADE-SVM分类预测：基于变体差分进化算法的SVM参数优化研究（Matlab代码实现内容概要：本文研究基于变体差分进化算法AL-SHADE优化支持向量机（SVM）的分类预测性能，重点解决SVM中关键参数（如惩罚因子C和核函数参数g）难以手动调优的问题。通过引入AL-SHADE算法，自动搜索最优参数组合，提升SVM在分类任务中的准确性与泛化能力。文中结合Matlab代码实现，展示了算法的完整流程，包括种群初始化、变异、交叉、选择机制及适应度函数设计，并通过实验验证了该方法相较于传统参数选择方式在分类精度上的优越性。; 适合人群：具备一定机器学习基础，熟悉支持向量机和优化算法原理，有一定Matlab编程经验的高校学生、科研人员或工程技术人员。; 使用场景及目标：①解决SVM模型参数调优困难问题，提升分类预测精度；②为智能优化算法（如差分进化及其变体）在机器学习超参数优化中的应用提供实践案例；③适用于需要高精度分类的科研项目或工程应用，如故障诊断、模式识别、金融风控等领域。; 阅读建议：建议读者结合提供的Matlab代码进行实践操作，深入理解AL-SHADE算法的运行机制及其与SVM的集成方式，重点关注适应度函数的设计与参数优化过程的可视化分析，以便迁移至其他模型优化任务中。
评论
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值