Bug 368040 - [remote debug] application output is truncated
Summary: [remote debug] application output is truncated
Status: NEW
Alias: None
Product: CDT
Classification: Tools
Component: cdt-debug-dsf-gdb (show other bugs)
Version: 8.0   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact: Jonah Graham CLA
URL:
Whiteboard:
Keywords:
Depends on: 371142 452356
Blocks:
  Show dependency tree
 
Reported: 2012-01-06 10:50 EST by Anna Dushistova CLA
Modified: 2020-09-04 15:22 EDT (History)
5 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Anna Dushistova CLA 2012-01-06 10:50:12 EST
Build Identifier: 

A project with the following source code:
#include <stdio.h>
#include <stdlib.h>

int main(void) {
    puts("!!!CDT application started!!!");
    int i;

    for (i=0; i<500; i++)
        printf("Counting %d\n", i);
    puts("!!!CDT application done!!!");

    return 0;
}

while debugged as a "Remote C/C++ Application" never gets to a "!!!CDT application done!!!"
line in the output unless there is a breakpoint set there or in "return 0" line.

If this application is ran remotely, it works as expected.

Reproducible: Always
Comment 1 Anna Dushistova CLA 2012-01-18 15:03:43 EST
GDB trace:
820,278 2-environment-cd /home/anna/runtime-New_configuration/test_output
820,278 2^done
820,316 (gdb) 
820,345 3-gdb-set breakpoint pending on
820,346 3^done
820,346 (gdb) 
820,348 4-gdb-set detach-on-fork on
820,348 4^done
820,348 (gdb) 
820,349 5-enable-pretty-printing
820,350 5^done
820,350 (gdb) 
820,351 6maintenance set python print-stack off
820,351 &"maintenance set python print-stack off\n"
820,351 6^done
820,351 (gdb) 
820,353 7source .gdbinit
820,354 &"source .gdbinit\n"
820,354 &".gdbinit: No such file or directory.\n"
820,354 7^error,msg=".gdbinit: No such file or directory."
820,354 (gdb) 
820,356 8-gdb-set auto-solib-add on
820,356 8^done
820,356 (gdb) 
820,360 9-file-exec-and-symbols --thread-group i1 /home/anna/runtime-New_configuration/test_output/D\
ebug/test_output
820,363 9^done
820,363 (gdb) 
820,365 10-target-select remote LOCALHOST:2345
820,407 &"warning: Can not parse XML target description; XML support was disabled at compile time\n"\

820,412 =thread-group-started,id="i1",pid="42000"
820,412 =thread-created,id="1",group-id="i1"
820,419 =library-loaded,id="/lib/ld-linux.so.2",target-name="/lib/ld-linux.so.2",host-name="/lib/ld-\
linux.so.2",symbols-loaded="0",thread-group="i1"
820,463 *stopped,frame={addr="0xb7770850",func="??",args=[],from="/lib/ld-linux.so.2"},thread-id="1"\
,stopped-threads="all",core="0"
820,463 ~"Created trace state variable $trace_timestamp for target's variable 1.\n"
820,463 10^connected
820,464 (gdb) 
820,656 11-list-thread-groups --available
820,773 &"warning: Can not parse XML OS data; XML support was disabled at compile time\n"
820,774 11^error,msg="Can not fetch data now.\n"
820,819 (gdb) 
821,045 12-break-insert --thread-group i1 -t -f main
821,056 12^done,bkpt={number="1",type="breakpoint",disp="del",enabled="y",addr="0x0804845d",func="ma\
in",file="../src/test_output.c",fullname="/home/anna/runtime-New_configuration/test_output/src/test_\
output.c",line="15",times="0",original-location="main"}
821,064 (gdb) 
821,239 13-exec-continue --thread-group i1
821,240 13^running
821,240 *running,thread-id="all"
821,240 (gdb) 
821,270 =library-loaded,id="/lib/libc.so.6",target-name="/lib/libc.so.6",host-name="/lib/libc.so.6",\
symbols-loaded="0",thread-group="i1"
821,271 *stopped,reason="breakpoint-hit",disp="del",bkptno="1",frame={addr="0x0804845d",func="main",\
args=[],file="../src/test_output.c",fullname="/home/anna/runtime-New_configuration/test_output/src/t\
est_output.c",line="15"},thread-id="1",stopped-threads="all",core="0"
821,271 (gdb) 
821,287 14-list-thread-groups
821,289 14^done,groups=[{id="i1",type="process",pid="42000",executable="/home/anna/runtime-New_confi\
guration/test_output/Debug/test_output",cores=["0"]}]
821,334 (gdb) 
821,588 15-list-thread-groups i1
821,590 15^done,threads=[{id="1",target-id="Thread 5118",frame={level="0",addr="0x0804845d",func="ma\
in",args=[],file="../src/test_output.c",fullname="/home/anna/runtime-New_configuration/test_output/s\
rc/test_output.c",line="15"},state="stopped",core="0"}]
821,593 (gdb) 
821,605 16-stack-info-depth --thread 1 11
821,605 16^done,depth="1"
821,605 (gdb) 
823,803 17-thread-info 1
823,803 18-list-thread-groups
823,806 17^done,threads=[{id="1",target-id="Thread 5118",frame={level="0",addr="0x0804845d",func="ma\
in",args=[],file="../src/test_output.c",fullname="/home/anna/runtime-New_configuration/test_output/s\
rc/test_output.c",line="15"},state="stopped",core="0"}]
823,807 (gdb) 
823,807 18^done,groups=[{id="i1",type="process",pid="42000",executable="/home/anna/runtime-New_confi\
guration/test_output/Debug/test_output",cores=["0"]}]
823,807 (gdb) 
824,086 19-stack-list-locals --thread 1 --frame 0 1
824,089 19^done,locals=[{name="i",value="-1217056780"}]
824,090 (gdb) 
824,553 20-stack-info-depth --thread 1
824,553 20^done,depth="1"
824,554 (gdb) 
824,609 21-var-create --thread 1 --frame 0 - * i
824,612 21^done,name="var1",numchild="0",value="-1217056780",type="int",thread-id="1",has_more="0"
824,612 (gdb) 
824,819 22-stack-list-frames --thread 1
824,820 22^done,stack=[frame={level="0",addr="0x0804845d",func="main",file="../src/test_output.c",fu\
llname="/home/anna/runtime-New_configuration/test_output/src/test_output.c",line="15"}]
824,821 (gdb) 
827,391 23-exec-continue --thread 1
827,392 23^running
827,393 *running,thread-id="all"
827,393 (gdb) 
827,416 =thread-group-exited,id="i1"
827,416 *stopped,reason="exited-normally"
827,416 (gdb) 
827,440 &"Quit\n"
827,466 24-gdb-exit
827,469 24^exit
Comment 2 Chandrayya CLA 2016-04-27 08:14:04 EDT
Changing "Console buffer size" value in Run/Debug > Console or the value of "Limit console output" in C/C++ > Build > Console has no effect.
Comment 3 Chandrayya CLA 2016-04-27 08:32:29 EDT
Dependent bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=371142 was marked as resolved now, is it fixed in latest eclipse CDT?

Not working in CDT 8.7.0
Comment 4 Chandrayya CLA 2017-01-10 08:21:14 EST
(In reply to Chandrayya Kumarswamimath from comment #3)
> Dependent bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=371142 was
> marked as resolved now, is it fixed in latest eclipse CDT?
> 
> Not working in CDT 8.7.0

Reproducible in latest CDT 9.0.0.201607151550 also. Not fixed yet.
Comment 5 Martin Oberhuber CLA 2017-01-11 05:52:17 EST
Note that since https://bugs.eclipse.org/bugs/show_bug.cgi?id=452356 was implemented in cdt-9.0 , RSE is no longer used as the communication channel at all for CDT remote debug -- it now uses org.eclipse.remote directly, which changes dependencies.

This is now a plain CDT / org.eclipse.remote issue. Please work with the CDT community debugging your use-case and getting it resolved.
Comment 6 Chandrayya CLA 2017-01-25 04:20:25 EST
(In reply to Martin Oberhuber from comment #5)
> Note that since https://bugs.eclipse.org/bugs/show_bug.cgi?id=452356 was
> implemented in cdt-9.0 , RSE is no longer used as the communication channel
> at all for CDT remote debug -- it now uses org.eclipse.remote directly,
> which changes dependencies.
> 
> This is now a plain CDT / org.eclipse.remote issue. Please work with the CDT
> community debugging your use-case and getting it resolved.

Thanks @Martin

@CDT team:
Give me some guidance/pointers so that I can contribute and fix this issue.