Emacs GDB garbled output

Emacs GDB garbled output

[Augusto Fraga Giachero]

Hello Emacs users!

I've been using Emacs + GDB (GUD) for debugging programs written in C 
since more or less 2 years. I generally recompile my projects by just 
invoking 'make' in the GDB shell.

What bothers me is that when the build process outputs a lot of text in 
a short period of time (such a compile error or warnings) the GDB shell 
doesn't catch all the text, and sometimes part of the text is displayed 
when the next command is executed. For example:

GDB under Emacs:
(gdb) make
gcc -MMD -c -g -Wall -I inc/ -Og src/testlib.c -o src/testlib.o
src/testlib.c:4:1: error: expected ‘ int isPrime(uint64_t num)
  stop
make: (gdb)

Standalone GDB:
gcc -MMD -c -g -Wall -I inc/ -Og src/testlib.c -o src/testlib.o
src/testlib.c:4:1: error: expected ‘=’, ‘,’, ‘;’, ‘asm’ or 
‘__attribute__’ before ‘int’
  int isPrime(uint64_t num)
  ^~~
make: *** [Makefile:27: src/testlib.o] Error 1

Anyone that have experienced this behavior known how to fix it?

Thanks,
Augusto Fraga Giachero.

Re: Emacs GDB garbled output

[Eli Zaretskii]

> From: Augusto Fraga Giachero <augustofg96@gmail.com>
> Date: Tue, 7 Mar 2017 09:08:33 -0300
> 
> I've been using Emacs + GDB (GUD) for debugging programs written in C 
> since more or less 2 years. I generally recompile my projects by just 
> invoking 'make' in the GDB shell.
> 
> What bothers me is that when the build process outputs a lot of text in 
> a short period of time (such a compile error or warnings) the GDB shell 
> doesn't catch all the text, and sometimes part of the text is displayed 
> when the next command is executed. For example:
> 
> GDB under Emacs:
> (gdb) make
> gcc -MMD -c -g -Wall -I inc/ -Og src/testlib.c -o src/testlib.o
> src/testlib.c:4:1: error: expected ‘ int isPrime(uint64_t num)
>   stop
> make: (gdb)

Which Emacs command do you use to invoke GDB?  Is it "M-x gud-gdb" or
"M-x gdb"?

If you used the latter, try the former instead.

Re: Emacs GDB garbled output

[Augusto Fraga Giachero]

You nailed it!

I was invoking gdb with 'M-x gdb'. Now using 'M-x gud-gdb' instead 
solved all my problems.

Thank you very much!

Augusto Fraga Giachero.

On 07-03-2017 12:48, Eli Zaretskii wrote:
>> From: Augusto Fraga Giachero <augustofg96@gmail.com>
>> Date: Tue, 7 Mar 2017 09:08:33 -0300
>>
>> I've been using Emacs + GDB (GUD) for debugging programs written in C
>> since more or less 2 years. I generally recompile my projects by just
>> invoking 'make' in the GDB shell.
>>
>> What bothers me is that when the build process outputs a lot of text in
>> a short period of time (such a compile error or warnings) the GDB shell
>> doesn't catch all the text, and sometimes part of the text is displayed
>> when the next command is executed. For example:
>>
>> GDB under Emacs:
>> (gdb) make
>> gcc -MMD -c -g -Wall -I inc/ -Og src/testlib.c -o src/testlib.o
>> src/testlib.c:4:1: error: expected ‘ int isPrime(uint64_t num)
>>    stop
>> make: (gdb)
> Which Emacs command do you use to invoke GDB?  Is it "M-x gud-gdb" or
> "M-x gdb"?
>
> If you used the latter, try the former instead.
>