3 ms·

I don't understand the downvote. Debugging C with gdb + emacs (albeit 20 years ago) was a decent experience. Even for a vi user...

ryanlm 10y ago
I really feel like a cowboy when I am debugging C with `gdb`
Roboprog 10y ago
I guess I don't understand downvotes in general. "Your opinion is SO offensive to me, that I must attempt to expunge it from existence" - or at least move it way down and grayed out. Alternative thinking considered harmful. Douchebags gonna douche, I guess...
- sctb 10y ago
  Please re-read the commenting guidelines carefully: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
  - Roboprog 10y ago
    Sorry, missed that second to the last one. No guidelines on downvoting, though???
    - tomku 10y ago
      You seem obsessed with other people's downvoting. Relax, seriously. If you think someone got a downvote they didn't deserve, upvote it yourself and move on. It's not your responsibility to police other people's voting behavior. Edit: If it really bugs you that much, post a comment backing the person up, but don't bring up the votes. It never adds anything except drama and distraction.
CJefferson 10y ago
It often feels like (as a non-emacs, non-vi user), that every conversation ever will end up at some point with a post that says "use emacs" or "use vi". These tend to have zero actual content (emacs is a text editor. How would I use it with gdb?), and not provide any evidence, or guidance.
- wbl 10y ago
  You just run it like any other interaction. In emacs if I want to compile a file I type M-x compile, and it asks me how. That creates a new buffer in which errors are linked to the original buffer. M-x gdb works the same way.
- Roboprog 10y ago
  Emacs would split the terminal screen, showing the gdb interpreter/prompt in the bottom pseudo-window where you could interact with it, and the source code for the current function in the top "window", with a visual "pointer" at the current line. I know you could put watch expressions into gdb, and I suspect there was a way to pull these into another emacs text window, as well. Gdb also had commands to list the stack and select a frame further down to see the callers data. I don't remember if the source code view (in emacs) would track the selected frame.

ryanlm 10y ago

I really feel like a cowboy when I am debugging C with `gdb`

Roboprog 10y ago

I guess I don't understand downvotes in general. "Your opinion is SO offensive to me, that I must attempt to expunge it from existence" - or at least move it way down and grayed out. Alternative thinking considered harmful. Douchebags gonna douche, I guess...

sctb 10y ago
Please re-read the commenting guidelines carefully: https://news.ycombinator.com/newsguidelines.html https://news.ycombinator.com/newsguidelines.html
- Roboprog 10y ago
  Sorry, missed that second to the last one. No guidelines on downvoting, though???
  - tomku 10y ago
    You seem obsessed with other people's downvoting. Relax, seriously. If you think someone got a downvote they didn't deserve, upvote it yourself and move on. It's not your responsibility to police other people's voting behavior. Edit: If it really bugs you that much, post a comment backing the person up, but don't bring up the votes. It never adds anything except drama and distraction.

CJefferson 10y ago

It often feels like (as a non-emacs, non-vi user), that every conversation ever will end up at some point with a post that says "use emacs" or "use vi". These tend to have zero actual content (emacs is a text editor. How would I use it with gdb?), and not provide any evidence, or guidance.

wbl 10y ago
You just run it like any other interaction. In emacs if I want to compile a file I type M-x compile, and it asks me how. That creates a new buffer in which errors are linked to the original buffer. M-x gdb works the same way.
Roboprog 10y ago
Emacs would split the terminal screen, showing the gdb interpreter/prompt in the bottom pseudo-window where you could interact with it, and the source code for the current function in the top "window", with a visual "pointer" at the current line. I know you could put watch expressions into gdb, and I suspect there was a way to pull these into another emacs text window, as well. Gdb also had commands to list the stack and select a frame further down to see the callers data. I don't remember if the source code view (in emacs) would track the selected frame.