'dq' command behavior has changed
See original GitHub issuegit bisect
suggests this was introduced in 2a09b30
Consider a simple program:
// main.c
char some_array[8] = "XXXXXXXX";
void main() {}
Built and run with:
$ gcc -ggdb main.c
$ gdb a.out
pwndbg> start
Previously, dq
could dump memory at the some_array
symbol:
After 2a09b30 it can’t, unless an ampersand is supplied before the symbol name:
Perhaps the original behavior was unintended, but I thought this was worth mentioning.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Behavior (automatic) - Collibra DQ User Guide
Using Behavioral Analytics (Change Detection) The number of DQ checks that the model encompasses. For example: A lookback of 10 means that the...
Read more >DQ Command: Display Pnode Queues - TechDocs
The DQ command displays the names of all or selected pnode queues, along with the number of jobs in each queue.
Read more >Establishing a Default Job Queue (DQ) - Unisys
Use the DQ (Default Queue) system command to establish a particular ... When a queue is established as the default queue, no queue...
Read more >DQMC Training Course | Health.mil
Class size is limited by Service. Persons who are not DQ Managers but work with data analysis and improving the quality of data...
Read more >BQ34Z950 - Texas Instruments
ENABLED WITH IMPEDANCE TRACK™ WITH OPTIONAL DQ INTERFACE ... 2Impedance Track is a trademark of Texas Instruments. ... POWER ON RESET BEHAVIOR.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I can’t speak for everyone but I imagine a lot of folks use pwndbg because it is not similar to the stock GDB experience. If that means I can type less characters, or a command is more intuitive/simple to use, then I would rather keep that behavior even if it isn’t in keeping with the original GDB syntax.