Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#79 extra linefeed when using GDB Segger J-Link debugging with output going to Eclipse

Next release
closed-fixed
None
5
2014-02-14
2014-01-23
Philip Gruebele
No

The logging output from GNU ARM J-Link Debugging Support (Experimental) 1.3.1.201401221754 contains an extra linefeed between each log entry as shown here, making overview of the log difficult because it scrolls out of view:

Setting breakpoint @ address 0x0000843A, Size = 2, BPHandle = 0x0002

Starting target CPU...

...Breakpoint reached @ address 0x0000843A

Reading all registers

Removing breakpoint @ address 0x0000843A, Size = 2

Read 4 bytes @ address 0x0000843A (Data = 0xFF79F7FF)

Reading 64 bytes @ address 0x20007FC0

Discussion

    • status: open --> open-accepted
    • assigned_to: Liviu Ionescu (ilg)
     
  • this probably must be a windows only problem, since I did not encounter it on OS X.

    I'll check it.

     
  • I ran the JLinkGDBServerCL.exe with the output redirected to a file and here is the result:

    00000000 53 45 47 47 45 52 20 4a 2d 4c 69 6e 6b 20 47 44 |SEGGER J-Link GD|
    00000010 42 20 53 65 72 76 65 72 20 56 34 2e 38 30 20 43 |B Server V4.80 C|
    00000020 6f 6d 6d 61 6e 64 20 4c 69 6e 65 20 56 65 72 73 |ommand Line Vers|
    00000030 69 6f 6e 0d 0d 0a 0d 0d 0a 4a 4c 69 6e 6b 41 52 |ion......JLinkAR|
    ...

    as you can see on the last line, the lines are separated by \r \r \n, which explains the empty lines in the Eclipse console.

    I reported this bug to SEGGER.

     
    • status: open-accepted --> closed-fixed
     
  • fixed by SEGGER