What is Reddit's opinion of GNU Project Debugger?

Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "arm-linux-gnueabihf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from gdb...(no debugging symbols found)...done. (gdb)

Anything that can be debugged with GDB and/or LLDB.

Examples of things that can be debugged with GDB/LLDB (very much non-exhaustive):

Native Linux software (written in C, C++, Fortran, etc)
iOS applications (written in Objective-C)
OSX applications
Android applications using the NDK
Native PS4 games (Sony actually has their own Visual Studio integration for this which does roughly the same thing as MIEngine)
Microcontroller software
Linux/Unix software ported to Windows using Mingw/Cygwin

Not to be harsh, but I was actually hoping to learn real tricks. Instead, it was pretty basic stuff imo (conditional breakpoints, really, who'd have thought ?!).

Instead, I suggest you spend a little time to just RTFM. Even quickly going over the important sections, you will learn a ton of "tricks".

Seems pretty bo~~x~~g standard, but why is it there at all and just a flash? It's there for like 4 frames at most. Maybe it's inferring that Elliot is debugging psychologically?

Not sure why the links would matter, it's not like they're a product of the show, but:

http://www.gnu.org/software/gdb/documentation/

http://www.gnu.org/software/gdb/bugs/

http://www.gnu.org/licenses/

Let me clarify. ViM is a very powerful text editor, but it lacks features (such as IntelliSense and an integrated debugger) that have become hallmark features of an IDE.

http://wrongsideofmemphis.com/2013/06/18/vim-as-ide-are-you-getting-the-good-parts/

Having done C/C++ development in Linux, I did use ViM to edit code, gcc to compile code, and gdb to debug code.

You will notice that writing gcc commands can be quite cumbersome, and there you will often want to do things like delete all compiled files and recompile. This is where you will start to use Make. Make lets you set "goals" and lists of things to do.

GCC and Make - A Tutorial onm how to compile, link and build https://www3.ntu.edu.sg/home/ehchua/programming/cpp/gcc_make.html

http://www.gnu.org/software/gdb/

>The one thing I could see being a problem on retail is that my server could crash, and with MINGW there is no debugger or crash report. So if my server crashes, I could be in the dark. Anyone know how I could get information on my program crashing with MINGW/ASIO/GCC++ ?

Er, I'm sure MinGW comes with gdb, the GNU debugger. http://www.gnu.org/software/gdb/ Have you looked at that?

Are you compiled for debugging? When I try rust-gdb this is what I get:

$ cat option.rs fn main() { let arg = std::env::args().nth(1); match arg { None => println!("no argument"), Some(s) => println!("argument: {}", s), } } $ cargo build Compiling option v0.1.0 (/home/bart/prj/rust/option) Finished dev [unoptimized + debuginfo] target(s) in 0.27s $ rust-gdb target/debug/option GNU gdb (Debian 8.2.1-2) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from target/debug/option...done. (gdb) break option::main Breakpoint 1 at 0x4ea7: file option.rs, line 2. (gdb) run x Starting program: /home/bart/prj/rust/option/target/debug/option x [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Breakpoint 1, option::main () at option.rs:2 2 let arg = std::env::args().nth(1); (gdb) n 2 let arg = std::env::args().nth(1); (gdb) n 4 None => println!("no argument"), (gdb) print arg $1 = core::option::Option<alloc::string::String>::Some("x") (gdb) quit

GDB

The GNU Project debugger allows you to see what is going on `inside' another program while it executes -- or what another program was doing at the moment it crashed.

GDB can do four main kinds of things (plus other things in support of these) to help you catch bugs in the act:

>❅ Start your program, specifying anything that might affect its behavior.

>❅ Make your program stop on specified conditions.

>❅ Examine what has happened, when your program has stopped.

>❅ Change things in your program, so you can experiment with correcting the effects of one bug and go on to learn about another.

Same issue with RPi 4B. Excessive ppoll. As soon as I attach to the gdm process with gdb it goes away.

GNU gdb (GDB) Fedora 10.1-2.fc33 Copyright (C) 2020 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "aarch64-redhat-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word". (gdb) attach 1207 Attaching to process 1207 [New LWP 1220] [New LWP 1222] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib64/libthread_db.so.1". 0x0000ffffb90163e4 in __aarch64_ldadd4_acq_rel () from /lib64/libglib-2.0.so.0 (gdb)

GDB doesn't support C#.
From http://www.gnu.org/software/gdb/:

What Languages does GDB Support?

GDB supports the following languages (in alphabetical order):

Ada

Assembly

C

C++

D

Fortran

Go

Objective-C

OpenCL

Modula-2

Pascal

Rust

u/kbielefe sorry to react after a long time i was very busy in some family works.

^(I tried to debug it like as you say but saying)

GNU gdb (Ubuntu 8.2-0ubuntu1) 8.2 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word"... ./d.out: No such file or directory. /home/atharva/core: No such file or directory. (gdb) r Starting program:
No executable file specified. Use the "file" or "exec-file" command. (gdb)

By the way, the binaries I've shown how to build here are just as easy to run using qemu.

bruce@rip:~/foo$ qemu-riscv64 foo bruce@rip:~/foo$ echo $? 42

qemu has a built in gdb server. So you can run in one terminal:

bruce@rip:~/foo$ qemu-riscv64 -g 1234 foo

And in another terminal:

bruce@rip:~/foo$ riscv64-unknown-elf-gdb foo -ex "target remote localhost:1234" GNU gdb (GDB) 8.3.0.20190516-git Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "--host=x86_64-pc-linux-gnu --target=riscv64-unknown-elf". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from foo... (No debugging symbols found in foo) Remote debugging using localhost:1234 0x00000000000100c4 in _start () (gdb) br main Breakpoint 1 at 0x1015a (gdb) c Continuing.

Breakpoint 1, 0x000000000001015a in main () (gdb) disas Dump of assembler code for function main: 0x0000000000010156 <+0>: li a0,42 => 0x000000000001015a <+4>: ret End of assembler dump. (gdb)

I still have kodi installed. I am trying to run gdb kodi but i am getting this error

kristhian@localhost ~> gdb kodi GNU gdb (GDB; openSUSE Tumbleweed) 8.3.1 Copyright (C) 2019 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-suse-linux". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://bugs.opensuse.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word"... "/usr/bin/kodi": not in executable format: file format not recognized (gdb) run Starting program:
No executable file specified. Use the "file" or "exec-file" command. (gdb)

also tried gdb firefox and got that same error.

Will try to find a solution, i want to fix this issues, openSUSE is my favorite distro. Thanks again for your help!

*replies in

$gdb ./program GNU gdb (Ubuntu 8.1-0ubuntu3) 8.1.0.20180409-git Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./program...done. (gdb) r Starting program: /home/riley/Desktop/workspace/C++/program

Program received signal SIGSEGV, Segmentation fault. 0x000055555555490d in main () at ./program.cpp:69

*

Isn't GDB incapable of debugging a program with PDB debug info? I tried GDB too. It even cannot debug hello.c compiled with clang on Windows.

C:\Code\hello> C:\Code\hello>gdb hello.exe GNU gdb (GDB) 8.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-w64-mingw32". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from hello.exe...(no debugging symbols found)...done. (gdb) (gdb) b main No symbol table is loaded. Use the "file" command. Make breakpoint pending on future shared library load? (y or [n]) (gdb) run Starting program: C:\Code\hello\hello.exe [New Thread 7124.0x678] Hello world! [New Thread 7124.0x3f98] [Thread 7124.0x3f98 exited with code 0] [Inferior 1 (process 7124) exited normally] (gdb)

uhm, i downloaded the source tar.gz, ran make && make install and now running filet gives me a segfault.

mss•~/git/filet-0.1.0» gdb filet
GNU gdb (Gentoo 8.2.1 p1) 8.2.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <https://bugs.gentoo.org/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./filet...(no debugging symbols found)...done.

(gdb) run Starting program: /home/mss/git/filet-0.1.0/filet

Program received signal SIGSEGV, Segmentation fault. 0x00007ffff7e68776 in __strlen_sse2 () from /lib64/libc.so.6

(gdb) where #0 0x00007ffff7e68776 in __strlen_sse2 () from /lib64/libc.so.6 #1 0x00005555555571e8 in main ()

Here's a part of the gdb log when I click the debug button in VSCode-

GNU gdb (Ubuntu 8.0.1-0ubuntu1) 8.0.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later &lt;http://gnu.org/licenses/gpl.html&gt;
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
&lt;http://www.gnu.org/software/gdb/bugs/&gt;.
Find the GDB manual and other documentation resources online at:
&lt;http://www.gnu.org/software/gdb/documentation/&gt;.
For help, type "help".
Type "apropos word" to search for commands related to "word".
Registered pretty printers for UE4 classes
=cmd-param-changed,param="pagination",value="off"
Stopped due to shared library event (no libraries added or removed)
Loaded '/lib64/ld-linux-x86-64.so.2'. Symbols loaded.

Program received signal SIGSEGV, Segmentation fault.
elf_dynamic_do_Rela (skip_ifunc=&lt;optimized out&gt;, lazy=0, nrelative=&lt;optimized out&gt;, relsize=26856, reladdr=&lt;optimized out&gt;, map=0x7ffff7ffe150) at do-rel.h:112
Execute debugger commands using "-exec &lt;command&gt;", for example "-exec info registers" will list registers in use (when GDB is the debugger)

$ gdb ./st GNU gdb (GDB) 8.0.1 Copyright (C) 2017 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-pc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from ./st...done. (gdb) break tresize Breakpoint 1 at 0x1b45e: file st.c, line 2515. (gdb) run Starting program: /opt/Code/stgl/st [Thread debugging using libthread_db enabled] Using host libthread_db library "/usr/lib/libthread_db.so.1".

Breakpoint 1, tresize (col=80, row=24) at st.c:2515 2515 int minrow = MIN(row, term.row); (gdb) bt #0 tresize (col=80, row=24) at st.c:2515 #1 0x000055555556f403 in tnew (col=80, row=24) at st.c:1055 #2 0x0000555555578c61 in main (argc=0, argv=0x7fffffffe850) at x.c:1851 (gdb) print minrow $1 = 0 (gdb) print row $2 = 24 (gdb) print term.row $3 = 0 (gdb)

sami@long:~$ cat /proc/cpuinfo | grep cpu cpu : 7447A, altivec supported

and as for the debugger info:

sami@long:~/ownCloud/projects$ gdb --args nodejs GNU gdb (Debian 7.10-1.1) 7.10 Copyright (C) 2015 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "powerpc-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word"... Reading symbols from nodejs...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/nodejs [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/powerpc-linux-gnu/libthread_db.so.1". [New Thread 0xb7fbc460 (LWP 1836)] [New Thread 0xb77bc460 (LWP 1837)] [New Thread 0xb6fbc460 (LWP 1838)] [New Thread 0xb67bc460 (LWP 1839)]

Program received signal SIGILL, Illegal instruction. 0x32218ce8 in ?? () (gdb) x/i $pc => 0x32218ce8: fcfid f1,f1 (gdb) x/x $pc 0x32218ce8: 0xfc200e9c (gdb)

Is there a more appropriate forum for this? I don't even know where to ask.

Did you actually try attaching to a process that exits with pthread_exit in the main thread such as the one in my post? No that doesn't work.

. gdb -p 25329 GNU gdb (Ubuntu 7.7.1-0ubuntu5~14.04.2) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu". Type "show configuration" for configuration details. For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>. Find the GDB manual and other documentation resources online at: <http://www.gnu.org/software/gdb/documentation/>. For help, type "help". Type "apropos word" to search for commands related to "word". Attaching to process 25329 Could not attach to process. If your uid matches the uid of the target process, check the setting of /proc/sys/kernel/yama/ptrace_scope, or try again as the root user. For more details, see /etc/sysctl.d/10-ptrace.conf warning: process 25329 is a zombie - the process has already terminated ptrace: Operation not permitted. (gdb) quit

. ltrace -f -p 25329 Cannot attach to pid 25329: Permission denied

. sudo ltrace -f -p 25329 [sudo] password for sstewartgallus: Cannot attach to pid 25329: No such file or directory

Just create projects of the empty type. Usually the folders are literally empty, besides .sln files etc.

If you want VS only for debugging possibilities, consider adding -g to your compiler flags (assuming gcc/mingw or clang) in Geany first and try out GDB. If it's not enough or if you don't like the interface you can still proceed with your transition to VS.

A human-readable version of machine code is known as Assembly. In simple terms, Assembly should have a more or less one-to-one correspondance with machine code. It consists of simple commands like arithmatic, if statements, go to staments, or moving items from into and out of cache. The way high level code (the "int x = 4" kind of thing) is translated to machine or assembly depends on the CPU and the compiler. If you are interested, you can use a program like GDB to produce the assembly commands for a section of an executable using the disassemble command. If you are really into optimizing your code with respect to machine resources or some other metric it can be an interesting way to look at exactly how the computer is interpreting your code.

Here's an example from when I try using it on my vigenere.c program:

jharvard@appliance (~/Dropbox/pset2): gdb ./vigenere GNU gdb (GDB) Fedora (7.6-34.fc19) Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-redhat-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /home/jharvard/Dropbox/pset2/vigenere...done. (gdb) break main Breakpoint 1 at 0x804872b: file vigenere.c, line 13. (gdb) run foo Starting program: /home/jharvard/Dropbox/pset2/vigenere foo

Breakpoint 1, main (argc=2, argv=0xbffff0d4) at vigenere.c:13 warning: Source file is more recent than executable. 13 // function prototypes (gdb) n

Breakpoint 1, main (argc=2, argv=0xbffff0d4) at vigenere.c:13 13 // function prototypes (gdb) n

Breakpoint 1, main (argc=2, argv=0xbffff0d4) at vigenere.c:13 13 // function prototypes (gdb) s

Breakpoint 1, main (argc=2, argv=0xbffff0d4) at vigenere.c:13 13 // function prototypes

You should learn how to use gdb. It will save you EONS in C debugging time.

http://www.gnu.org/software/gdb/

1 Delete is slightly wrong

temp = currP -> next; /temp points to the node which has to be removed/ currP->next = temp->next; temp->prev = currP; /* should be temp->next->prev = currP

2 Why do you store message as an array? Casting arrays to and from pointers is okay but if it's a pointer, you should store it as a pointer.

What is Reddit's opinion of GNU Project Debugger?
From 3.5 billion Reddit comments

➔ GNU Project Debugger website

By popularity on Reddit, this Service is:

24 reviews of this app found across Reddit:

What is Reddit's opinion of GNU Project Debugger? From 3.5 billion Reddit comments

➔ GNU Project Debugger website

By popularity on Reddit, this Service is:

24 reviews of this app found across Reddit:

What is Reddit's opinion of GNU Project Debugger?
From 3.5 billion Reddit comments