Sponsored Content
Full Discussion: Abrupt GDB Behaviour
Top Forums UNIX for Dummies Questions & Answers Abrupt GDB Behaviour Post 302792489 by shamrock on Wednesday 10th of April 2013 01:14:39 PM
Old 04-10-2013
Did you compile it with the debugging "-g" switch on...
 

10 More Discussions You Might Find Interesting

1. Programming

GDB or DBX??

Which is better?? I have always been a gdb fan.. But ppl say dbx is beter better for debugging the core.. Do all GDB lovers agree to it??? :cool: (1 Reply)
Discussion started by: jyotipg
1 Replies

2. Programming

gdb Tutorials

Can anyone give me the link to a website having gdb tutorials (for advanaced debugging & shortcuts) http://www.burneddowndays.com/talk/YaBBImages/rolleyes.gif (1 Reply)
Discussion started by: wojtyla
1 Replies

3. Solaris

gdb for SunOS 5.6

I want to install gdb on SunOS 5.6 machine. Where can i download from ? (1 Reply)
Discussion started by: shafi2all
1 Replies

4. UNIX for Advanced & Expert Users

Gdb:

Hi, This is a simple question on GDB. Given a core file, how can you check which process has dumped the core? Regards - Krishna (1 Reply)
Discussion started by: krishnamurthig
1 Replies

5. UNIX for Advanced & Expert Users

Gdb

Hi All, I wanted to know if there is a core file generated and I am not sure for which Binary it is generated . Can I use gdb to debug the core file ? Thanks. (1 Reply)
Discussion started by: shubhranshu
1 Replies

6. UNIX for Advanced & Expert Users

Using Gdb

Hi All, I am trying to execute a binary and it is giving Segmentation Fault. Can I use gdb to debug this error? Secondly there is no core file generated , so when I an trying to run gdb with the binary only I am not able to set any breakpoints. When I am running the gdb and the I am... (1 Reply)
Discussion started by: shubhranshu
1 Replies

7. Programming

gdb not found

Hello, I am having problem with debugging my code. I am writing a C code and then I compile it with the Makefile. I make a target file and then copy it in my Robot(Khepera III) and then run the program over there. I compile it ofcorse on my machine and then copy the compiled file in the... (10 Replies)
Discussion started by: mind@work
10 Replies

8. Programming

gdb help

i have created some break points in gdb. let's say.... b sqlcxt how can i know the breakpoint name of sqlcxt ??? (1 Reply)
Discussion started by: lipun4u
1 Replies

9. Programming

Qemu + gdb

Hi, I got: host machine: RedHat (RHEL6) virtual machine: RedHat (RHEL6) I run (on host machine): qemu-system-x86_64 ...... -S -s after that i run (on host machine): gdb target remote localhost:1234 set architecture i386:x86-64 and then i can use (on host machine) 'ctrl + c' to... (2 Replies)
Discussion started by: Chrisdot
2 Replies

10. Programming

Gdb backtrace

Hi, all I try to understand the output from gdb Program received signal SIGABRT, Aborted. *** glibc detected *** /home/sys_cbo/dev/zif/bin/Debug/zifd: free(): invalid pointer: 0x00007fffac04d3d0 *** how should i read this? (gdb) backtrace #0 0x0000003015e32925 in raise () from... (1 Reply)
Discussion started by: huvcbo
1 Replies
DBSYM(8)						    BSD System Manager's Manual 						  DBSYM(8)

NAME
dbsym -- copy kernel symbol table into db_symtab space SYNOPSIS
dbsym [-v] [-b bfdname] kernel DESCRIPTION
dbsym is used to copy the symbol table in a newly linked kernel into the db_symtab array (in the data section) so that the ddb(4) kernel debugger can find the symbols. This program is only used on systems for which the boot program does not load the symbol table into memory with the kernel. The space for these symbols is reserved in the data segment using a config option like: options SYMTAB_SPACE=72000 The size of the db_symtab array (the value of SYMTAB_SPACE) must be at least as large as the kernel symbol table. If insufficient space is reserved, dbsym will refuse to copy the symbol table. To recognize kernel executable format, the -b flag specifies BFD name of kernel. If the -v flag is given, dbsym will print out status information as it is copying the symbol table. Note that debugging symbols are not useful to the ddb(4) kernel debugger, so to minimize the size of the kernel, one should either compile the kernel without debugging symbols (no -g flag) or use the strip(1) command to strip debugging symbols from the kernel before dbsym is used to copy the symbol table. The command strip -d netbsd will strip out debugging symbols. SEE ALSO
strip(1), ddb(4) BSD
November 9, 2001 BSD
All times are GMT -4. The time now is 10:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy