help-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re:Re: a question about gdb in emacs


From: x_uch
Subject: Re:Re: a question about gdb in emacs
Date: Wed, 4 Jun 2014 23:26:05 +0800 (CST)

Because it only have "<br/>SQLite version 3.8.4.3 2014-04-03 16:53:12<br/>Enter 
".help" for usage hints.<br/>Connected to a transient in-memory 
database.<br/>Use ".open FILENAME" to reopen on a persistent 
database.<br/>sqlite&gt;<br/>" for output while run sqlite3, so i put 
fflush(stdout) before line 3816,3822,3823,3824 in shell.c,but the problem still 
have...
At 2014-06-04 10:54:59, "Eli Zaretskii" <eliz@gnu.org> wrote:
>> Date: Wed, 4 Jun 2014 16:36:31 +0800 (CST)
>> From: x_uch  <x_uch@163.com>
>> 
>> While i debuged the application in windows that use emacs, the buffer of 
>> emacs can't get the output,but in system, everything is ok. I don't know 
>> where the error is in me or the emacs.
>> in windows , prommpt can get the output like this:
>> 
>> 
>> and in emacs ,gdb buffer like this:
>> 
>> Here is the application, i download from sqlite site,web address 
>> http://www.sqlite.org/2014/sqlite-amalgamation-3080403.zip .In windows ,i 
>> compiled it using mingw,
>> using "gcc -g -o sqlite3 shell.c sqlite3.c" to build sqlite3.exe
>> 
>> I tried other app, source code:
>> #include <stdio.h>
>> typedef struct {
>>   float a;
>>   float b;
>> } substruct;
>> 
>> struct {
>>   int i;
>>   substruct r;
>> } c;
>> 
>> myproc(n)
>> {
>>   int p;
>>   p = 2*n;
>>   printf("Two times %d is %d\n", n, p);
>> }
>> 
>> main() {
>>   int n = 4;
>>   int m[10] = {0,1,4,9,16,25,36,49,64,81};
>>   n = 5;
>>   myproc(n);
>>   c.i = 1;
>>   c.r.a = 0.5;
>>   c.r.b = 0.25;
>> }
>> saved it to test.c,build by gcc -o test test.c -g
>> in windows and emacs gdb all can get the output "Two times 5 is 10"
>> so i think the problem in emacs,but i have not enough time to read the 
>> source code......
>
>Try adding
>
>  fflush (stdout);
>
>after each printf call.  This might well be a buffering issue.
>

reply via email to

[Prev in Thread] Current Thread [Next in Thread]