Sponsored Content
Operating Systems AIX Which debugger can i use to debug XL CC compiler build Post 302311465 by bakunin on Tuesday 28th of April 2009 07:01:58 PM
Old 04-28-2009
Quote:
Originally Posted by kittu1979
Hi ,
I know dbx,gdb debuggers
These are the debuggers you can use. There is also - depending on what type of software you are writing - the kdb (kernel debugger) which might be of value for you.

Be careful with kdb, it is quite easy to crash the system by manipulating kernel data structures, though.

I hope this helps.
 

8 More Discussions You Might Find Interesting

1. Programming

How to debug C source file using GVD debugger

Anyone pls. help !!! I want to debug C source file using GVD debugger. However, I am unable to find the way to debug source files. Thanks in advance (2 Replies)
Discussion started by: argupta
2 Replies

2. Programming

C compiler to build Sparc/Solaris binaries on Linux

Just that the Subject says. I am looking for a C compiler for Linux x86 that will allow me to compile a C source code file and the resulting binary will be able to run on a Sparc running Solaris. Thanks. (2 Replies)
Discussion started by: lyonsd
2 Replies

3. UNIX for Dummies Questions & Answers

xl C/C++ compiler to GCC compiler

Hi, we are converting from IBM-AIX(xl c/c++ compiler) to Linux(GCC complier). As a part of this i need to change the CFLAGS. The xl c/c++ complier CFLAGS is CFLAGS := $(CDEBUG) $(PROJECT_INCLUDE_DIRS) $(COBJECT_MODE) -qcpluscmt -qmakedep -qcheck=all \ -qalign=bit_packed $(LINT_FLAGS)... (0 Replies)
Discussion started by: pbattu1
0 Replies

4. Programming

How to debug with wdb debugger a cobol program?

Hi Forum, i have such a question. I have a cobol program which is calling a C program and in that C program i get a core dump:(. I want to investigate what is the issue using WDB debuger, but a dont see the code from COBOL program in the debuger, when i run the debugger with the exe!!! ... (2 Replies)
Discussion started by: vovan
2 Replies

5. Programming

How Can a Machine Reads a Compiler Since A Compiler is Written in Text! Not Binaries?

To make a programming language you need a compiler, so what was the first programming language and how was is created if you need the compiler first? The compiler itself is considered as a high language comparing to the machine! since the compiler is not created in 1's and 0's... Eventhough i... (12 Replies)
Discussion started by: f.ben.isaac
12 Replies

6. Programming

Alternative debugger to GNU insight debugger

GNU insight debugger is not available now a days and it is required to debug/inspect assembly code as written in the book Assembly Language Programming step by step in Linux so my question is; is there any alternative to insight that I can use instead of insight in which I can get the same... (5 Replies)
Discussion started by: vectrum
5 Replies

7. UNIX for Dummies Questions & Answers

Adding SDK Build on Kernel Source Build

Hi, So I downloaded this kernel source and was able to build it successfully. But I want to add this SDK source code inside, can anyone help me how to do this? Note that the SDK source can be built by itself. I added the SDK in the main Makefile: init-y := init/ #added SDK... (0 Replies)
Discussion started by: h0ujun
0 Replies

8. Shell Programming and Scripting

Build.xml invocation by Build Script

Hi I have a build.xml file and I can run it on Windows via cmd. Now I want to write a script to invoke the same. Is there a way to do this? (1 Reply)
Discussion started by: ankur328
1 Replies
KGDB(1) 						    BSD General Commands Manual 						   KGDB(1)

NAME
kgdb -- kernel debugger SYNOPSIS
kgdb [-a | -f | -fullname] [-b rate] [-q | -quiet] [-v] [-w] [-d crashdir] [-c core | -n dumpnr | -r device] [kernel [core]] DESCRIPTION
The kgdb utility is a debugger based on gdb(1) that allows debugging of kernel core files. The options are as follows: -a Increase the annotation level. An annotation level of 1 features the historical -fullname option of gdb(1). This is useful when running kgdb in Emacs. The -f or -fullname options are supported for backward compatibility as well. -b rate Set the baudrate to rate. -q Suppress printing of the banner when the debugger starts. The -quiet form is supported for compatibility as well. -v Increase verbosity. -w Opens kmem-based targets in read-write mode. (This is identical to what --wcore used to do in previous gdb versions for FreeBSD.) -d crashdir Use crashdir instead of the default, /var/crash to locate kernel core dump files in. The name vmcore. plus the dump number will be appended to determine the actual dump file name. -c core Explicitly use core as the core dump file. -n dumpnr Use the kernel core dump file numbered dumpnr for debugging. -r device Use device to connect kgdb to for a remote debugging session. The -c, -n, and -r options are mutually exclusive. Optionally, the name of the kernel symbol file and the name of the core dump file can be supplied on the command-line as positional argu- ments. If no kernel symbol file name has been given, the symbol file of the currently running kernel will be used. If no core dump file has been specified through either of the options or the last command-line argument, /dev/mem will be opened to allow debugging the currently run- ning kernel. FILES
/dev/mem Default memory image to open if no core dump file has been specified. /var/crash Default directory to locate kernel core dump files. SEE ALSO
gdb(1) HISTORY
The kgdb utility first appeared in its current form in FreeBSD 5.3. BSD
October 11, 2006 BSD
All times are GMT -4. The time now is 01:41 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy