Microsoft MVP성태의 닷넷 이야기
글쓴 사람
정성태 (techsharer at outlook.com)
홈페이지
첨부 파일
 

C# - 닷넷 응용 프로그램에서 DB2 Express-C 데이터베이스 사용 (3) - ibmcom/db2express-c 컨테이너 사용

지난 글에서는,

C# - 닷넷 응용 프로그램에서 DB2 Express-C 데이터베이스 사용 (2)
; https://www.sysnet.pe.kr/2/0/1408

윈도우에 생성한 DB2 환경을 예로 들었는데 이번에는 docker에 이미 설치된 "ibmcom/db2express-c" 컨테이너로 예를 들겠습니다. 이를 위해 db2 환경이 실행 중인 컨테이너 내에 bash를 실행시켜 들어갑니다.

# docker ps  | grep db2
a3cf35df65ba db2_db "/entrypoint.sh db2s…"   5 months ago  Up 13 days  22/tcp, 0.0.0.0:50000->50000/tcp  db2_db_1

// ibmcom/db2express-c 이미지가 실행 중인 컨테이너 ID: a3cf35df65ba

# docker exec -it a3cf35df65ba /bin/bash

그래도 혹시 모르니 db2가 적절하게 설치되었는지 db2val을 찾아,

# find / -name db2val
/home/db2inst1/sqllib/bin/db2val

확인해 보고,

# /home/db2inst1/sqllib/bin/db2val
DBI1379I  The db2val command is running. This can take several minutes.

DBI1335I  Installation file validation for the DB2 copy installed at
      /home/db2inst1/sqllib was successful.

DBI1343I  The db2val command completed successfully. For details, see
      the log file /tmp/db2val-200305_062706.log.

이후 db2 실행 파일을 찾아 DB 제어를 위한 명령행 환경으로 진입합니다.

# find / -name db2
/home/db2inst1/sqllib/bin/db2
...[생략]...

# /home/db2inst1/sqllib/bin/db2
...[생략]...

db2 =>

db2 명령행까지 들어왔다면 이제 게임 끝이군요, (아래의 예는 생성된 DB 목록을 조회하는 것으로) 여타 DB 관리처럼 이후 진행을 하면 됩니다.

db2 => list db directory

 System Database Directory

 Number of entries in the directory = 1

Database 1 entry:

 Database alias                       = MYTESTDB
 Database name                        = MYTESTDB
 Local database directory             = /home/db2inst1
 Database release level               = 10.00
 Comment                              =
 Directory entry type                 = Indirect
 Catalog database partition number    = 0
 Alternate server hostname            =
 Alternate server port number         =

여기까지 해서 컨테이너의 TCP 매핑, Database 이름을 구했으면 IBM.Data.DB2.dll의 DB2Connection 객체에 사용할 연결 문자열이 다음과 같이 구해집니다.

Server=testdbsrv:50000;Database=MYTESTDB;UID=...;PWD=...

이후의 제어는 그냥 편안하게 "IBM Data Studio"를 이용해 원격에서 제어하시는 것도 ^^ 좋겠습니다.




이제 환경 구성하면서 오류가 발생한 상황을 정리해 보겠습니다. 우선, DB2Connection.Open에서 다음과 같은 오류가 발생한다면?

Server Error in '/' Application.
SQL1159  Initialization error with DB2 .NET Data Provider, reason code 2, tokens C:\Test\WebApp\bin\db2app64.dll, , Process Owner: TESTAD\TESTUSR
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.InvalidOperationException: SQL1159  Initialization error with DB2 .NET Data Provider, reason code 2, tokens C:\Test\WebApp\bin\db2app64.dll, , Process Owner: TESTAD\TESTUSR

Source Error:

Line 48:             {
Line 49:                 connection.ConnectionString = connectionString;
Line 50:                 connection.Open();
Line 51: 

Source File: C:\Test\WebApp\DB2Default.aspx.cs    Line: 50

Stack Trace:

[InvalidOperationException: SQL1159  Initialization error with DB2 .NET Data Provider, reason code 2, tokens C:\Test\WebApp\bin\db2app64.dll, , Process Owner: TESTAD\TESTUSR]
   IBM.Data.DB2.DB2ConnPool.Open(DB2Connection connection, String& szConnectionString, DB2ConnSettings& ppSettings, Object& ppConn) +7637
   IBM.Data.DB2.DB2Connection.Open() +577
   WebApp.DB2Default.Page_Load(Object sender, EventArgs e) in C:\Test\WebApp\DB2Default.aspx.cs:50
   System.Web.UI.Control.OnLoad(EventArgs e) +108
   System.Web.UI.Control.LoadRecursive() +90
   System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1607

Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.8.4075.0}

해당 프로젝트가 빌드된 /bin 폴더에 db2app64.dll 파일이 없기 때문입니다.




IBM Data Studio에서 db2 서버의 주소, 데이터베이스, 계정 명과 비밀번호를 입력 후 "Test Connection"을 했는데 다음과 같은 오류가 발생한다면?

A connection attempt was unsuccessful.

Summary

SQL4499N  A fatal error occurred that resulted in a disconnect from the data source.

Try the following suggestions to help solve the problem:

Ensure that the data server has been started.
Check that the database name used is the actual database name and not an alias name.
Check that the host is a valid name or IP address, and that the port number is valid for communication with the data server.
To further diagnose the problem, return to the Properties section and use the Tracing page to enable tracing. Contact the database administrator and provide the trace and other support information available.
Full message content: [jcc][t4][2057][11264][4.14.113] 응용프로그램 서버(AS)가 연결을 거부했습니다. 
찾을 수 없거나 트랜잭션을 지원하지 않은 TESTDB 데이터베이스에 액세스하려고 시도했습니다.

Explanation

<b>Explanation:</b><br/><br/>An attempt was made to access a database that was not found, has not been started, or does not support transactions.
<br/><b>User response:</b><br/><br/>Ensure that the specified database name exists in the system database directory. If the database name does not exist in the system database directory, either the database does not exist or the database name has not been cataloged. If needed, issue a db2start command and then resubmit the current command.
SQLSSTATE: 08004

Support

Connection Properties

Database : TESTDB
URL :  jdbc:db2://192.168.100.50:50000/TESTDB:retrieveMessagesFromServerOnGetMessage=true;securityMechanism=4;
User name : TESTUSR
Password : (Not Shown)

Environment

Driver class name = com.ibm.db2.jcc.DB2Driver
Driver version = 4.14.113
Driver JAR file path = C:\Program Files\ibm\SDPShared\plugins\com.ibm.datatools.db2_2.1.503.v20121002_1809\driver\db2jcc4.jar;C:\Program Files\ibm\SDPShared\plugins\com.ibm.datatools.db2_2.1.503.v20121002_1809\driver\db2jcc_license_cisuz.jar
Operating system name = Windows Server 8
Operating system architecture = amd64
Operating system version = 6.2
JVM implementation vendor = IBM Corporation
JVM runtime = Java(TM) SE Runtime Environment
Java version = JRE 1.7.0 IBM J9 2.6 Windows Server 8 amd64-64 20120809_118929 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR2_20120809_0948_B118929
JIT  - r11.b01_20120808_24925
GC   - R26_Java726_SR2_20120809_0948_B118929
J9CL - 20120809_118929
Launcher = C:\Program Files\ibm\DS3.2.0\eclipse.exe

Stack Trace

com.ibm.db2.jcc.am.DisconnectNonTransientConnectionException: [jcc][t4][2057][11264][4.14.113] 응용프로그램 서버(AS)가 연결을 거부했습니다. 
찾을 수 없거나 트랜잭션을 지원하지 않은 TESTDB 데이터베이스에 액세스하려고 시도했습니다.  ERRORCODE=-4499, SQLSTATE=08004com.ibm.db2.jcc.am.ed.a(Unknown Source)
com.ibm.db2.jcc.am.ed.a(Unknown Source)
com.ibm.db2.jcc.t4.y.u(Unknown Source)
com.ibm.db2.jcc.t4.y.n(Unknown Source)
com.ibm.db2.jcc.t4.y.a(Unknown Source)
com.ibm.db2.jcc.t4.y.a(Unknown Source)
com.ibm.db2.jcc.t4.b.c(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.<init>(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.open(Unknown Source)
org.eclipse.datatools.enablement.ibm.db2.internal.luw.JDBCLUWConnectionFactory.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.handleTestConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.access$6(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage$10.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.jface.window.Window.runEventLoop(Unknown Source)
org.eclipse.jface.window.Window.open(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.actions.NewDBConnectionHandler.execute(Unknown Source)
org.eclipse.ui.internal.handlers.HandlerProxy.execute(Unknown Source)
org.eclipse.core.commands.Command.executeWithChecks(Unknown Source)
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(Unknown Source)
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(Unknown Source)
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(Unknown Source)
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem.access$19(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
org.eclipse.ui.internal.Workbench.access$4(Unknown Source)
org.eclipse.ui.internal.Workbench$7.run(Unknown Source)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
org.eclipse.equinox.launcher.Main.run(Unknown Source)
org.eclipse.equinox.launcher.Main.main(Unknown Source)

데이터베이스 (위의 메시지에서는 TESTDB)가 실제로 있는지 확인할 필요가 있습니다.




또는, 다음과 같이 오류가 발생한다면?

A connection attempt was unsuccessful.

Summary

SQL4214N  A connection authorization failure has occurred.

Try the following suggestions to help solve the problem:

Ensure that the user name and password are correct. These values are defined in the New Connection wizard or, for an existing connection, on the General page in the Driver Properties section.
Ensure that the user name is valid. For example, on UNIX and Linux platforms, user names must be all lowercase. <a href="http://publib.boulder.ibm.com/infocenter/db2luw/v9r7/index.jsp?topic=/com.ibm.db2.luw.admin.dbobj.doc/doc/c0007245.html">Review the DB2 general naming rules</a>.
If you recently changed permissions on critical DB2 files, such as db2ckpw, or moved to a new fix pack, the db2iupdt command that updates the instance might not have been run. Contact your DBA to run db2iupdt with the InstName parameter to update the instance.
Full message content: [jcc][t4][201][11237][4.14.113] 연결 권한 부여에 실패했습니다. 이유: 보안 메커니즘이 지원되지 않습니다.

Explanation

<b>Explanation:</b><br/><br/>An error occurred during security processing. Either the user name specified or the password specified, or both, are invalid.
<br/><b>User response:</b><br/><br/>Ensure that the specified user name and password are correct.
SQLSSTATE: 28000

Support

Connection Properties

Database : MYTESTDB
URL :  jdbc:db2://192.168.100.50:50000/MYTESTDB:retrieveMessagesFromServerOnGetMessage=true;securityMechanism=4;
User name : TESTUSR
Password : (Not Shown)

Environment

Driver class name = com.ibm.db2.jcc.DB2Driver
Driver version = 4.14.113
Driver JAR file path = C:\Program Files\ibm\SDPShared\plugins\com.ibm.datatools.db2_2.1.503.v20121002_1809\driver\db2jcc4.jar;C:\Program Files\ibm\SDPShared\plugins\com.ibm.datatools.db2_2.1.503.v20121002_1809\driver\db2jcc_license_cisuz.jar
Operating system name = Windows Server 8
Operating system architecture = amd64
Operating system version = 6.2
JVM implementation vendor = IBM Corporation
JVM runtime = Java(TM) SE Runtime Environment
Java version = JRE 1.7.0 IBM J9 2.6 Windows Server 8 amd64-64 20120809_118929 (JIT enabled, AOT enabled)
J9VM - R26_Java726_SR2_20120809_0948_B118929
JIT  - r11.b01_20120808_24925
GC   - R26_Java726_SR2_20120809_0948_B118929
J9CL - 20120809_118929
Launcher = C:\Program Files\ibm\DS3.2.0\eclipse.exe

Stack Trace

com.ibm.db2.jcc.am.SqlInvalidAuthorizationSpecException: [jcc][t4][201][11237][4.14.113] 연결 권한 부여에 실패했습니다. 이유: 보안 메커니즘이 지원되지 않습니다. ERRORCODE=-4214, SQLSTATE=28000com.ibm.db2.jcc.am.ed.a(Unknown Source)
com.ibm.db2.jcc.am.ed.a(Unknown Source)
com.ibm.db2.jcc.am.ed.a(Unknown Source)
com.ibm.db2.jcc.t4.b.f(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.y.b(Unknown Source)
com.ibm.db2.jcc.t4.y.a(Unknown Source)
com.ibm.db2.jcc.t4.y.a(Unknown Source)
com.ibm.db2.jcc.t4.b.c(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.b(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.a(Unknown Source)
com.ibm.db2.jcc.t4.b.<init>(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2SimpleDataSource.getConnection(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
com.ibm.db2.jcc.DB2Driver.connect(Unknown Source)
org.eclipse.datatools.connectivity.drivers.jdbc.JDBCConnection.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.internalCreateConnection(Unknown Source)
org.eclipse.datatools.connectivity.DriverConnectionBase.open(Unknown Source)
org.eclipse.datatools.enablement.ibm.db2.internal.luw.JDBCLUWConnectionFactory.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionFactoryProvider.createConnection(Unknown Source)
org.eclipse.datatools.connectivity.internal.ConnectionProfile.createConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.handleTestConnection(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage.access$6(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.NewDatabaseConnnectionWizardPage$10.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.jface.window.Window.runEventLoop(Unknown Source)
org.eclipse.jface.window.Window.open(Unknown Source)
com.ibm.datatools.connection.internal.ui.databases.actions.NewDBConnectionHandler.execute(Unknown Source)
org.eclipse.ui.internal.handlers.HandlerProxy.execute(Unknown Source)
org.eclipse.core.commands.Command.executeWithChecks(Unknown Source)
org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(Unknown Source)
org.eclipse.ui.internal.handlers.HandlerService.executeCommand(Unknown Source)
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(Unknown Source)
org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem.handleWidgetSelection(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem.access$19(Unknown Source)
org.eclipse.ui.menus.CommandContributionItem$5.handleEvent(Unknown Source)
org.eclipse.swt.widgets.EventTable.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Widget.sendEvent(Unknown Source)
org.eclipse.swt.widgets.Display.runDeferredEvents(Unknown Source)
org.eclipse.swt.widgets.Display.readAndDispatch(Unknown Source)
org.eclipse.ui.internal.Workbench.runEventLoop(Unknown Source)
org.eclipse.ui.internal.Workbench.runUI(Unknown Source)
org.eclipse.ui.internal.Workbench.access$4(Unknown Source)
org.eclipse.ui.internal.Workbench$7.run(Unknown Source)
org.eclipse.core.databinding.observable.Realm.runWithDefault(Unknown Source)
org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.PlatformUI.createAndRunWorkbench(Unknown Source)
org.eclipse.ui.internal.ide.application.IDEApplication.start(Unknown Source)
org.eclipse.equinox.internal.app.EclipseAppHandle.run(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(Unknown Source)
org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
org.eclipse.core.runtime.adaptor.EclipseStarter.run(Unknown Source)
sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
java.lang.reflect.Method.invoke(Unknown Source)
org.eclipse.equinox.launcher.Main.invokeFramework(Unknown Source)
org.eclipse.equinox.launcher.Main.basicRun(Unknown Source)
org.eclipse.equinox.launcher.Main.run(Unknown Source)
org.eclipse.equinox.launcher.Main.main(Unknown Source)

접속 계정의 ID나 비밀번호를 다시 체크해 볼 필요가 있습니다.




[이 글에 대해서 여러분들과 의견을 공유하고 싶습니다. 틀리거나 미흡한 부분 또는 의문 사항이 있으시면 언제든 댓글 남겨주십시오.]





[최초 등록일: ]
[최종 수정일: 3/5/2020 ]

Creative Commons License
이 저작물은 크리에이티브 커먼즈 코리아 저작자표시-비영리-변경금지 2.0 대한민국 라이센스에 따라 이용하실 수 있습니다.
by SeongTae Jeong, mailto:techsharer@outlook.com

비밀번호

댓글 쓴 사람
 




1  2  3  4  5  6  7  8  9  [10]  11  12  13  14  15  ...
NoWriterDateCnt.TitleFile(s)
12105정성태1/8/2020678디버깅 기술: 153. C# - PEB를 조작해 로드된 DLL을 숨기는 방법
12104정성태1/9/20201096DDK: 9. 커널 메모리를 읽고 쓰는 NT Legacy driver와 C# 클라이언트 프로그램 [4]
12103정성태4/23/20201873DDK: 8. Visual Studio 2019 + WDK Legacy Driver 제작- Hello World 예제 [1]파일 다운로드2
12102정성태1/6/20201267디버깅 기술: 152. User 권한(Ring 3)의 프로그램에서 _ETHREAD 주소(및 커널 메모리를 읽을 수 있다면 _EPROCESS 주소) 구하는 방법
12101정성태1/8/2020787.NET Framework: 876. C# - PEB(Process Environment Block)를 통해 로드된 모듈 목록 열람
12100정성태1/3/2020545.NET Framework: 875. .NET 3.5 이하에서 IntPtr.Add 사용
12099정성태1/3/2020773디버깅 기술: 151. Windows 10 - Process Explorer로 확인한 Handle 정보를 windbg에서 조회
12098정성태9/10/2020769.NET Framework: 874. C# - 커널 구조체의 Offset 값을 하드 코딩하지 않고 사용하는 방법 [3]
12097정성태1/2/2020581디버깅 기술: 150. windbg - Wow64, x86, x64에서의 커널 구조체(예: TEB) 구조체 확인
12096정성태1/2/2020796디버깅 기술: 149. C# - DbgEng.dll을 이용한 간단한 디버거 제작
12095정성태12/27/2019940VC++: 135. C++ - string_view의 동작 방식
12094정성태12/26/2019807.NET Framework: 873. C# - 코드를 통해 PDB 심벌 파일 다운로드 방법
12093정성태12/26/2019987.NET Framework: 872. C# - 로딩된 Native DLL의 export 함수 목록 출력파일 다운로드1
12092정성태12/25/2019844디버깅 기술: 148. cdb.exe를 이용해 (ntdll.dll 등에 정의된) 커널 구조체 출력하는 방법
12091정성태12/25/20191175디버깅 기술: 147. pdb 파일을 다운로드하기 위한 symchk.exe 실행에 필요한 최소 파일 [1]
12090정성태12/24/2019798.NET Framework: 871. .NET AnyCPU로 빌드된 PE 헤더의 로딩 전/후 차이점
12089정성태12/23/2019681디버깅 기술: 146. gflags와 _CrtIsMemoryBlock을 이용한 Heap 메모리 손상 여부 체크
12088정성태12/23/2019571Linux: 28. Linux - 윈도우의 "Run as different user" 기능을 shell에서 실행하는 방법
12087정성태12/21/2019684디버깅 기술: 145. windbg/sos - Dictionary의 entries 배열 내용을 모두 덤프하는 방법 (do_hashtable.py)
12086정성태12/20/2019845디버깅 기술: 144. windbg - Marshal.FreeHGlobal에서 발생한 덤프 분석 사례
12085정성태12/20/2019701오류 유형: 586. iisreset - The data is invalid. (2147942413, 8007000d) 오류 발생 - 두 번째 이야기 [1]
12084정성태12/21/2019805디버깅 기술: 143. windbg/sos - Hashtable의 buckets 배열 내용을 모두 덤프하는 방법 (do_hashtable.py)
12083정성태12/17/20191184Linux: 27. linux - lldb를 이용한 .NET Core 응용 프로그램의 메모리 덤프 분석 방법 [2]
12082정성태12/17/2019869오류 유형: 585. lsof: WARNING: can't stat() fuse.gvfsd-fuse file system
12081정성태12/16/20191022개발 환경 구성: 465. 로컬 PC에서 개발 중인 ASP.NET Core 웹 응용 프로그램을 다른 PC에서도 접근하는 방법 [2]
12080정성태12/16/20191185.NET Framework: 870. C# - 프로세스의 모든 핸들을 열람
1  2  3  4  5  6  7  8  9  [10]  11  12  13  14  15  ...