15,471
社区成员
发帖
与我相关
我的任务
分享关于可调式的dll
请问
类似于VC 界面里 project ---> code generation -->debug Multithreaded DLL
这样的命令
来生成 debug版的dll
CL 命令 里面有没有
如果 有 下面的 命令
link -out:stunnel.dll /DLL ws2_32.lib gdi32.lib user32.lib shell32.lib comdlg32.lib libeay32.lib ssleay32.lib advapi32.lib stunnel.obj ssl.obj client.obj protocol.obj sthreads.obj log.obj options.obj sselect.obj gui.obj resources.res
还需要进行 怎么样的修改 谢谢，最近 搞这玩意 头都大了，
请过来人 给小弟 讲讲 谢谢
如果 对于 Stunnel 有 熟悉 的 并且 能给予指点下 小弟万分荣幸啊
QQ 346966702
备注 stunnel就行
类似于VC 界面里 project ---> code generation -->debug Multithreaded DLL
这样的命令
来生成 debug版的dll
CL 命令 里面有没有
如果 有 下面的 命令
link -out:stunnel.dll /DLL ws2_32.lib gdi32.lib user32.lib shell32.lib comdlg32.lib libeay32.lib ssleay32.lib advapi32.lib stunnel.obj ssl.obj client.obj protocol.obj sthreads.obj log.obj options.obj sselect.obj gui.obj resources.res
还需要进行 怎么样的修改 谢谢，最近 搞这玩意 头都大了，
请过来人 给小弟 讲讲 谢谢
如果 对于 Stunnel 有 熟悉 的 并且 能给予指点下 小弟万分荣幸啊
QQ 346966702
备注 stunnel就行
...全文
请发表友善的回复…
发表回复
mcaok 2010-04-22
- 打赏
- 举报
写一个Dialog程序，然后把Dll附加到Dialog上。在Dialog中LoadLibrary上打断点运行到此处之后F11就进入Dll了。可以单步调试了。详细点说就是新建一个Workspaces然后添加一个Dll工程和一个Dialog工程。Dialog中写加载DLL代码。然后在Project Settings中选中DLL工程，点开Debug页在Executable for debug session:中选择Dialog生成的exe文件。在build工具栏中选择Dll工程和debug模式。在你想要的地方加断点。F5就OK了。
尹成 2010-04-21
- 打赏
- 举报
认真看一下MSDN关于编译器设置
/Z7, /Zi, /ZI (Debug Information Format)
Select the type of debugging information created for your program and whether this information is kept in object (.obj) files or in a program database (PDB).
Copy
/Z{7|i|I}
Remarks
--------------------------------------------------------------------------------
The options are described in the following table.
None
Produces no debugging information, so compilation is faster.
/Z7
Produces an .obj file containing full symbolic debugging information for use with the debugger. The symbolic debugging information includes the names and types of variables, as well as functions and line numbers. No .pdb file is produced.
For distributors of third-party libraries, there is an advantage to not having a .pdb file. However, the .obj files for the precompiled headers are necessary during the link phase, and debugging. If there is only type information (and no code) in the .pch object files, you will also have to compile with /Yl (Inject PCH Reference for Debug Library).
/Zi
Produces a program database (PDB) that contains type information and symbolic debugging information for use with the debugger. The symbolic debugging information includes the names and types of variables, as well as functions and line numbers.
/Zi does not affect optimizations. However, /Zi does imply /debug; see /DEBUG (Generate Debug Info) for more information.
Type information is placed in the .pdb file, and not in the .obj file.
You can use /Gm (Enable Minimal Rebuild) with /Zi, whereas /Gm is not available when compiling with /Z7.
When compiling with /Zi and /clr, the DebuggableAttribute attribute will not be placed in the assembly metadata; you must specify it in source code, if you want it. This attribute can affect the runtime performance of the application. For more information about how the Debuggable attribute affects performance and how you can modify the performance impact, see Making an Image Easier to Debug.
/ZI
Produces a program database, as described above, in a format that supports the Edit and Continue feature. If you want to use Edit and Continue debugging, you must use this option. Because most optimizations are incompatible with Edit and Continue, using /ZI disables any #pragma optimize statements in your code.
/ZI causes /Gy (Enable Function-Level Linking) and /FC (Full Path of Source Code File in Diagnostics) to be used in your compilation.
/ZI is not compatible with /clr (Common Language Runtime Compilation).
Note
/ZI is only available in the compiler targeting x86; this compiler option is not available in the compilers targeting x64 or Itanium Processor Family (IPF).
The compiler names the program database project.pdb. If you compile a file without a project, the compiler creates a database named VCx0.pdb., where x is the major version of Visual C++ in use. The compiler embeds the name of the PDB in each .obj file created using this option, pointing the debugger to the location of symbolic and line-number information. When you use this option, your .obj files will be smaller, because debugging information is stored in the .pdb file rather than in .obj files.
If you create a library from objects that were compiled using this option, the associated .pdb file must be available when the library is linked to a program. Thus, if you distribute the library, you must distribute the PDB.
To create a library that contains debugging information without using .pdb files, you must select the compiler's C 7.0-Compatible (/Z7) option. If you use the precompiled headers options, debugging information for both the precompiled header and the rest of the source code is placed in the PDB. The /Yd option is ignored when the Program Database option is specified.
To set this compiler option in the Visual Studio development environment
Open the project's Property Pages dialog box. For details, see How to: Open Project Property Pages.
Click the C/C++ folder.
Click the General property page.
Modify the Debug Information Format property.
To set this compiler option programmatically
See DebugInformationFormat.
/Z7, /Zi, /ZI (Debug Information Format)
Select the type of debugging information created for your program and whether this information is kept in object (.obj) files or in a program database (PDB).
Copy
/Z{7|i|I}
Remarks
--------------------------------------------------------------------------------
The options are described in the following table.
None
Produces no debugging information, so compilation is faster.
/Z7
Produces an .obj file containing full symbolic debugging information for use with the debugger. The symbolic debugging information includes the names and types of variables, as well as functions and line numbers. No .pdb file is produced.
For distributors of third-party libraries, there is an advantage to not having a .pdb file. However, the .obj files for the precompiled headers are necessary during the link phase, and debugging. If there is only type information (and no code) in the .pch object files, you will also have to compile with /Yl (Inject PCH Reference for Debug Library).
/Zi
Produces a program database (PDB) that contains type information and symbolic debugging information for use with the debugger. The symbolic debugging information includes the names and types of variables, as well as functions and line numbers.
/Zi does not affect optimizations. However, /Zi does imply /debug; see /DEBUG (Generate Debug Info) for more information.
Type information is placed in the .pdb file, and not in the .obj file.
You can use /Gm (Enable Minimal Rebuild) with /Zi, whereas /Gm is not available when compiling with /Z7.
When compiling with /Zi and /clr, the DebuggableAttribute attribute will not be placed in the assembly metadata; you must specify it in source code, if you want it. This attribute can affect the runtime performance of the application. For more information about how the Debuggable attribute affects performance and how you can modify the performance impact, see Making an Image Easier to Debug.
/ZI
Produces a program database, as described above, in a format that supports the Edit and Continue feature. If you want to use Edit and Continue debugging, you must use this option. Because most optimizations are incompatible with Edit and Continue, using /ZI disables any #pragma optimize statements in your code.
/ZI causes /Gy (Enable Function-Level Linking) and /FC (Full Path of Source Code File in Diagnostics) to be used in your compilation.
/ZI is not compatible with /clr (Common Language Runtime Compilation).
Note
/ZI is only available in the compiler targeting x86; this compiler option is not available in the compilers targeting x64 or Itanium Processor Family (IPF).
The compiler names the program database project.pdb. If you compile a file without a project, the compiler creates a database named VCx0.pdb., where x is the major version of Visual C++ in use. The compiler embeds the name of the PDB in each .obj file created using this option, pointing the debugger to the location of symbolic and line-number information. When you use this option, your .obj files will be smaller, because debugging information is stored in the .pdb file rather than in .obj files.
If you create a library from objects that were compiled using this option, the associated .pdb file must be available when the library is linked to a program. Thus, if you distribute the library, you must distribute the PDB.
To create a library that contains debugging information without using .pdb files, you must select the compiler's C 7.0-Compatible (/Z7) option. If you use the precompiled headers options, debugging information for both the precompiled header and the rest of the source code is placed in the PDB. The /Yd option is ignored when the Program Database option is specified.
To set this compiler option in the Visual Studio development environment
Open the project's Property Pages dialog box. For details, see How to: Open Project Property Pages.
Click the C/C++ folder.
Click the General property page.
Modify the Debug Information Format property.
To set this compiler option programmatically
See DebugInformationFormat.
lmxmx 2010-04-21
- 打赏
- 举报
任何DLL都可以单步啊？
你在生成DLL的时候，可以选择Debug方式，而且DLL连接后都有符号文件……
你在生成DLL的时候，可以选择Debug方式，而且DLL连接后都有符号文件……
sayang 2010-04-20
- 打赏
- 举报
再写个exe调用该dll，在dll的项目属性中调试选项下的命令 和工作目录填写为debug版的exe，单步 ok
rendao0563 2010-04-20
- 打赏
- 举报
是要直接调试dll？ 随便加个宿主就行了。
an_bachelor 2010-04-20
- 打赏
- 举报
http://msdn.microsoft.com/en-us/library/958x11bc.aspx
an_bachelor 2010-04-20
- 打赏
- 举报
/Zi /ZI参数都可以加上调试信息
jokey514 2010-04-20
- 打赏
- 举报
顶一下！
jack_doson 2010-04-20
- 打赏
- 举报
[Quote=引用 7 楼 xiuxianshen 的回复:]
你是要生成dll还是要做什么?
[/Quote]
我想要能进行 单步调试运行的 dll
你是要生成dll还是要做什么?
[/Quote]
我想要能进行 单步调试运行的 dll
xiuxianshen 2010-04-15
- 打赏
- 举报
你是要生成dll还是要做什么?
wnx_u 2010-04-15
- 打赏
- 举报
/DEBUG
jack_doson 2010-04-15
- 打赏
- 举报
[Quote=引用 4 楼 xianglitian 的回复:]
我把这个帖子给你转到 进程/线程/DLL 版
希望你的问题早日得到解决
[/Quote]
谢谢
我把这个帖子给你转到 进程/线程/DLL 版
希望你的问题早日得到解决
[/Quote]
谢谢
向立天 2010-04-15
- 打赏
- 举报
我把这个帖子给你转到 进程/线程/DLL 版
希望你的问题早日得到解决
希望你的问题早日得到解决
jack_doson 2010-04-15
- 打赏
- 举报
[Quote=引用 2 楼 vc_zsy 的回复:]
帮顶···不会···
[/Quote]
楼上的 FS 童鞋 给点饼干吧
帮顶···不会···
[/Quote]
楼上的 FS 童鞋 给点饼干吧
VC_ZSY 2010-04-15
- 打赏
- 举报
帮顶···不会···
z8y8x 2010-04-15
- 打赏
- 举报
不懂友情顶一下
