| 여기는 지구 달 나와라 오바. (0) | 2010.05.27 |
|---|---|
| 반포대교 분수 야경 (달빛무지개분수) (2) | 2010.05.21 |
| 달, 별 (0) | 2010.05.17 |
| 보헤미안 안녕~ (12) | 2010.05.16 |
| 한강, 노을 그리고 구름 (6) | 2010.05.15 |
| 자살에 대한 짧은 생각 - 강 / 바다 (0) | 2010.05.24 |
|---|---|
| 복귀자 신고? (0) | 2010.05.22 |
| netffice를 기억하시나요? (0) | 2010.05.12 |
| 페이스북 가입! (4) | 2010.04.28 |
| 비온다. (8) | 2010.04.26 |
| Sound Blaster Audigy2 드라이버 (SB0240) (2) | 2010.06.28 |
|---|---|
| 빵집 4.0이 나왔어요!!! (2) | 2010.06.24 |
| rawrite for windows (2) | 2010.05.05 |
| REC(Reverse Engineering Compiler) / Decompiler (0) | 2010.05.01 |
| WOL(Wake On LAN) (4) | 2010.04.28 |
| 일본어 유니코드 (0) | 2014.06.09 |
|---|---|
| 라틴 어군 관련 조사 (0) | 2012.09.10 |
| Hebrew code range (unicode) (0) | 2010.04.30 |
| 태국어(Thai) / 히브리어(Hebrew) (0) | 2010.04.23 |
| 한글오토마타 관련 문서 (2) | 2010.03.04 |
 Selecting a TargetSelecting a target involves choosing a target for debugging and setting connection interface options for the target. Common targets include: "Exec" for native debuggers, "Remote/Serial" for establishing a connection to a target board via a serial line, "Remote/TCP" for TCP connections, and "Simulator" for connections to the simulator. There may be more depending on the configuration of the debugger being used. In general, "remote" targets are always serial connections which require the user to specify the serial port and baud rate to be used for the connection and "remote/tcp" targets are always TCP connections which require specifying the hostname and port number of the machine to which to connect. Depending upon configuration, there may be numerous serial- and TCP-based connections. These always follow the naming convention target/Serial and target/TCP. To select a target, choose one of the available targets from the dropdown menu in the Connection Frame. Then specify the interface options for this target: selecting the baudrate and serial port from the dropdown menus (serial targets only) or entering the hostname and port number (TCP targets only). [출처 : insight - About GDB - target window] |
| gdb 디버깅 타겟을 인자와 함께 실행하기 (0) | 2022.10.17 |
|---|---|
| gdb break (0) | 2021.04.09 |
| insight/gdb 우분투에서 컴파일하기 실패 - insight/gdb compiling on ubuntu failed (2) | 2010.05.18 |
| gdb / gdbserver 접속명령어 (0) | 2010.05.18 |
| insight(gdb) 아키텍쳐별 차이점(?) (0) | 2010.05.18 |
| WARNING: `makeinfo' is missing on your system. You should only need it if you modified a `.texi' or `.texinfo' file, or any other file indirectly affecting the aspect of the manual. The spurious call might also be the consequence of using a buggy `make' (AIX, DU, IRIX). You might want to install the `Texinfo' package or the `GNU make' package. Grab either from any GNU archive site. $ makeinfo 'makeinfo' 프로그램은 현재 설치되어 있지 않습니다. 다음을 입력하여 이를 설치할 수 있습니다: sudo apt-get install texinfo |
| configure: error: no termcap library found |
| gcc -c -g -O2 -I. -I.././gdb -I.././gdb/config -DLOCALEDIR="\"/usr/local/share/locale\"" -DHAVE_CONFIG_H -I.././gdb/../include/opcode -I.././gdb/../readline/.. -I../bfd -I.././gdb/../bfd -I.././gdb/../include -I../libdecnumber -I.././gdb/../libdecnumber -DMI_OUT=1 -DGDBTK -DTUI=1 -Wall -Wdeclaration-after-statement -Wpointer-arith -Wformat-nonliteral -Wno-pointer-sign -Wno-unused -Wno-switch -Wno-char-subscripts -Werror linux-nat.c cc1: warnings being treated as errors linux-nat.c: In function ‘linux_nat_info_proc_cmd’: linux-nat.c:2879: error: ignoring return value of ‘fgets’, declared with attribute warn_unused_result |
| WARNING: `bison' missing on your system. You should only need it if you modified a `.y' file. You may need the `Bison' package in order for those modifications to take effect. You can get `Bison' from any GNU archive site. |
| ada-lex.c missing and flex not available. |
| gcc -g -O2 \ -o gdb gdb.o libgdb.a \ ../readline/libreadline.a ../opcodes/libopcodes.a ../bfd/libbfd.a ../libiberty/libiberty.a ../libdecnumber/libdecnumber.a ../libgui/src/libgui.a -L/home/morpheuz/src/insight/itcl/itcl -litcl3.2 -L/home/morpheuz/src/insight/itcl/itk -litk3.2 -L/home/morpheuz/src/insight/tk/unix -ltk8.4 -Wl,-rpath,/usr/local/lib -L/home/morpheuz/src/insight/tcl/unix -ltcl8.4 -lX11 -ldl -lieee -lm -lncurses -lm ../libiberty/libiberty.a -ldl -rdynamic libgdb.a(ada-lang.o): In function `parse': /home/morpheuz/src/insight/gdb/ada-lang.c:10972: undefined reference to `ada_parse' libgdb.a(ada-lang.o):(.rodata+0xda0): undefined reference to `ada_error' |
| gdb break (0) | 2021.04.09 |
|---|---|
| gdb/insight target window (0) | 2010.05.19 |
| gdb / gdbserver 접속명령어 (0) | 2010.05.18 |
| insight(gdb) 아키텍쳐별 차이점(?) (0) | 2010.05.18 |
| gdb cross compile 관련 (0) | 2010.05.18 |
| ABI는 변수의 크기, 메모리 정렬, 스택에 넣는 순서(calling convention), 시스템 콜의 번호, 그리고 완전한 OS ABI의 경우 목적파일의 이진포맷, 프로그램 라이브러리 등을 포괄한다. 예를 들어 인텔 이진 호환 표준(iBCS) 와 같은 완전한 ABI에서는 ABI를 지원하는 하나의 운영체제에서 그러한 다른 시스템으로 공유 라이브러가 존재하고 이와 비슷한 선결조건을 충족시킨다면 어떠한 수정도 가하지 않고 실행될수 있다. 다른 ABI들은 컴파일러와 동일 플랫폼에서 사이의 C++ 이름 맹글링, 예외 전파, 그리고 스택에 넣는 순서(calling convention)과 같은 것들을 표준화 하였지만, 교차 플랫폼 호환성을 요구하지 않는다. ABI는 호출할 루틴의 라이브러리를 정의하고, 자료구조를 조작하고, (종종 언어에 특화된) 특정 API를 사용하는 프로그램의 작성에 사용되는 오프젝트 클래스와 같은 API(Application Programming Interface)와는 혼동해서는 안된다. ABIs cover details such as data type, size, and alignment; the calling convention, which controls how functions' arguments are passed and return values retrieved; the system call numbers and how an application should make system calls to the operating system; and in the case of a complete operating system ABI, the binary format of object files, program libraries and so on. A complete ABI, such as the Intel Binary Compatibility Standard (iBCS),[1] allows a program from one operating system supporting that ABI to run without modifications on any other such system, provided that necessary shared libraries are present, and similar prerequisites are fulfilled. Other ABIs standardize details such as the C++ name mangling,[2] exception propagation,[3] and calling convention between compilers on the same platform, but do not require cross-platform compatibility. An ABI should not be confused with an application programming interface (API) which defines a library of routines to call, data structures to manipulate, and/or object classes to use in the construction of an application using that particular (often language specific) API. [링크 : http://en.wikipedia.org/wiki/Application_binary_interface] |
| ABI는 소프트웨어 개발시 많은 장점을 가지고 있다. 예를 들면 마이크로소프트의 윈
도 98에서 사용되던 응용 프로그램이 윈
도 XP와 호환되는 것은 마이크로소프트가 ABI를 지원하기 때문이다. 유닉스 계통인 리눅스, BSD(FreeBSD/OpenBSD/NetBSD)에서
도 ABI를 제공하고 하지만 아직 완벽하다고 할 수는 없다. [링크 : http://ko.wikipedia.org /wiki/응용_프로그램_2진_인터페이스] |
| VLIW - Very Long Instruction Word (0) | 2013.10.08 |
|---|---|
| 펜타일(Pentile) 방식 디스플레이 (2) | 2011.10.15 |
| EFI 와 BIOS (0) | 2011.07.22 |
| KiB / MiB (0) | 2011.07.22 |
| GPS / A-GPS / S-GPS / D-GPS (2) | 2010.10.23 |
| To use a TCP
connection instead of a serial line: target> gdbserver host:2345 emacs foo.txt The only difference from the previous example is the first argument, specifying that you are communicating with the host gdb via TCP. The `host:2345' argument means that gdbserver is to expect a TCP connection from machine `host' to local TCP port 2345. (Currently, the `host' part is ignored.) [링크 : http://sourceware.org/gdb/current/onlinedocs/gdb/Server.html#Server] |
| target remote host:port target remote tcp:host:port Debug using a TCP connection to port on host. The host may be either a host name or a numeric IP address; port must be a decimal number. The host could be the target machine itself, if it is directly connected to the net, or it might be a terminal server which in turn has a serial line to the target. target remote udp:host:port Debug using UDP packets to port on host. For example, to connect to UDP port 2828 on a terminal server named manyfarms: target remote udp:manyfarms:2828 When using a UDP connection for remote debugging, you should keep in mind that the `U' stands for “Unreliable”. UDP can silently drop packets on busy or unreliable networks, which will cause havoc with your debugging session. [링크 : http://sourceware.org/gdb/current/onlinedocs/gdb/Connecting.html#Connecting] |
| gdb/insight target window (0) | 2010.05.19 |
|---|---|
| insight/gdb 우분투에서 컴파일하기 실패 - insight/gdb compiling on ubuntu failed (2) | 2010.05.18 |
| insight(gdb) 아키텍쳐별 차이점(?) (0) | 2010.05.18 |
| gdb cross compile 관련 (0) | 2010.05.18 |
| gdb 스크립트를 이용한 자동화 - automation using script on gdb (3) | 2009.09.01 |
| insight/gdb 우분투에서 컴파일하기 실패 - insight/gdb compiling on ubuntu failed (2) | 2010.05.18 |
|---|---|
| gdb / gdbserver 접속명령어 (0) | 2010.05.18 |
| gdb cross compile 관련 (0) | 2010.05.18 |
| gdb 스크립트를 이용한 자동화 - automation using script on gdb (3) | 2009.09.01 |
| gdb 명령어 - next / step / [엔터] (0) | 2009.07.01 |
| # ./configure
--build=i686-linux --host=arm-linux --target=arm-linux
--prefix=/nfsroot/gdb # ./configure --build=i686-linux --host=i686-linux --target=arm-linux --prefix=$PWD/build [링크 : http://blog.daum.net/joell/11772014] |
| --- gdb/gdbserver # ./configure --build=i686-linux --host=sh4-linux --target=sh4-linux --prefix=/home/morpheuz/st7109/target # make # make install n=`echo gdbserver | sed 's,^,sh4-linux-,'`; \ if [ x$n = x ]; then n=gdbserver; else true; fi; \ /bin/sh ./../../mkinstalldirs /home/morpheuz/st7109/target/bin; \ /usr/bin/install -c gdbserver /home/morpheuz/st7109/target/bin/$n; \ /bin/sh ./../../mkinstalldirs /home/morpheuz/st7109/target/man/man1; \ /usr/bin/install -c -m 644 ./gdbserver.1 /home/morpheuz/st7109/target/man/man1/$n.1 |
| gdb / gdbserver 접속명령어 (0) | 2010.05.18 |
|---|---|
| insight(gdb) 아키텍쳐별 차이점(?) (0) | 2010.05.18 |
| gdb 스크립트를 이용한 자동화 - automation using script on gdb (3) | 2009.09.01 |
| gdb 명령어 - next / step / [엔터] (0) | 2009.07.01 |
| gdb help (0) | 2009.06.26 |
|
