GDB 8.1 Released • Hacker News Board

Re: GDB 8.1 Released

#11

Post by harikb » Wed, Jan 31, 2018, 6:22 PM UTC

lucb1e wrote: post #6

dmm wrote: post #4

Earlier quoted context omitted.

MD5 is fine for verifying a download is not corrupted, so that's probably the intended use.

For that purpose, TCP already includes a CRC32. I'd say cryptographic hashes are generally meant for more than corrupted downloads.

File checksums are typically used when the checksum is still on the master site but the file could be in untrusted mirrors. TCP level stuff is useless in those scenarios.

Re: GDB 8.1 Released

#12

Post by gramstrong » Wed, Jan 31, 2018, 6:28 PM UTC

purplezooey wrote: post #10

heh. Has anyone ever used gdb to debug Pascal? :)

I might have used it to debug Ada, which is like Pascal, back when I was in school.

Re: GDB 8.1 Released

#13

Post by kazinator » Wed, Jan 31, 2018, 6:30 PM UTC

I'd really like a way for a program to have an API for interacting with GDB: with that it could tell "I'm running under a debugger". There would be a file descriptor which talks to the debugger, if the debugger is present. Output sent to it goes to the debugger and perhaps it could obtain input from the debugger also. Maybe the API could provide some introspection: the program could ask what breakpoints have been set and things like that.

Re: GDB 8.1 Released

#14

Post by rivert » Wed, Jan 31, 2018, 6:36 PM UTC

purplezooey wrote: post #10

heh. Has anyone ever used gdb to debug Pascal? :)

I have to, on a regular basis actually and I'm glad gdb and FPC work well together.

Re: GDB 8.1 Released

#15

Post by xuhu » Wed, Jan 31, 2018, 6:38 PM UTC

starti, rbreak and ptype sound good even if they've been available as idioms before.

Re: GDB 8.1 Released

#16

Post by wazari972 » Wed, Jan 31, 2018, 6:42 PM UTC

kazinator wrote: post #13

I'd really like a way for a program to have an API for interacting with GDB: with that it could tell "I'm running under a debugger". There would be a file descriptor which talks to the debugger, if the debugger is present. Output sent to it goes to the debugger and perhaps it could obtain input from the debugger also. Maybe the API could provide some introspection: the program could ask what breakpoints have been set…

this is not particularly hard to do with the Python interface: you define structures that are known by the process and the Python module + global variables, then you set an internal (silent) breakpoint on a given 'event' function. In the program you fill the structure with some queries, and in the Python breakpoint callback, you process it as you need. This is the way multi-thread debugging work (used to at least), shared library detection as well...

Re: GDB 8.1 Released

#17

Post by erk__ » Wed, Jan 31, 2018, 6:46 PM UTC

zython wrote: post #5

> New shortcuts for TUI Single-Key mode: 'i' for stepi, and 'o' for nexti; TUI really is one of the best features to really get into gdb. visually stepping through the disassembly really makes debugging more appealing, I really wish they dont abandon this aspect of gdb

My favorite visual gdb interface is the one build into emacs esspecially with gbd-many-mode

Re: GDB 8.1 Released

#18

Post by agumonkey » Wed, Jan 31, 2018, 6:56 PM UTC

rivert wrote: post #14

purplezooey wrote: post #10

heh. Has anyone ever used gdb to debug Pascal? :)

I have to, on a regular basis actually and I'm glad gdb and FPC work well together.

Nice to hear, I have a pascal lisp project I need to revive, having gdb on my side would help

Re: GDB 8.1 Released

#19

Post by guipsp » Wed, Jan 31, 2018, 7:01 PM UTC

harikb wrote: post #11

lucb1e wrote: post #6

Earlier quoted context omitted.

For that purpose, TCP already includes a CRC32. I'd say cryptographic hashes are generally meant for more than corrupted downloads.

File checksums are typically used when the checksum is still on the master site but the file could be in untrusted mirrors. TCP level stuff is useless in those scenarios.

So is md5

Re: GDB 8.1 Released

#20

Post by modeless » Wed, Jan 31, 2018, 7:08 PM UTC

kazinator wrote: post #13

I'd really like a way for a program to have an API for interacting with GDB: with that it could tell "I'm running under a debugger". There would be a file descriptor which talks to the debugger, if the debugger is present. Output sent to it goes to the debugger and perhaps it could obtain input from the debugger also. Maybe the API could provide some introspection: the program could ask what breakpoints have been set…

Having the program behave differently under a debugger is a great way to introduce bugs that disappear when the debugger is present. Any features of this type would have to be completely optional.