gsingh93

Fixing this is a bit trickier than I first thought. If the output from displaying a register in the second column can't fit in the column, it gets put on...

Yes, exactly. This happened to me today, it's not a great experience. But I'm also concerned about truncating the displayed register value, so I'm not sure what to do here.

@disconnect3d what do you think this command should be called? Once I know that I think this will be easy to finish up.

Was implemented in https://github.com/pwndbg/pwndbg/pull/1940, closing.

I think https://github.com/pwndbg/pwndbg/pull/1841 implemented a version of this with some extra features. I haven't used it much, but maybe this issue should be closed?

Another idea, we could add these two commands (or one `ctx-section` command with two subcommands): - `ctx-add-section []`: Appends `` to context-sections by default, otherwise inserts it at the specified...

I'm fine with @disconnect3d's suggestion of `ctx [on|off]`, essentially adding this feature to the existing command.

I don't think so, the QEMU testing scripts are different than the other GDB tests and I believe they still run serially.

Colors can be written to plaintext files through terminal escape/control codes (try `grep` or `rg` with `--color=always` and write to a file to see an example), but GDB doesn't support...

Not an expert in how this works, but I have two ideas: - We can have different limits for the number of chain elements to display vs. the number of...