Linux Jlink GDBServer - SO_REUSEADDR

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • Linux Jlink GDBServer - SO_REUSEADDR

    Hello,

    could be possible to bind sockets with SO_REUSEADDR? Sometimes the Jlink GDBServer quits with Seg fault and I have to wait until the TIME_WAIT expires. (I do not want to restart my network...).

    ref: serverfault.com/questions/3298…ose-a-socket-in-time-wait


    Reading 64 bytes @ address 0x1000A3C0
    Reading 64 bytes @ address 0x1000A380
    Read 2 bytes @ address 0x0000432E (Data = 0x48AC)
    Read 2 bytes @ address 0x00004330 (Data = 0xF003)
    Read 2 bytes @ address 0x00004C94 (Data = 0xF04F)
    GDB closed TCP/IP connection
    Connected to 127.0.0.1
    Segmentation fault (core dumped)
    /var/log/syslog
    Oct 11 12:56:09 ubuntu kernel: [369167.324070] JLinkGDBServer[19062]: segfault at 5257d949 ip 0807161d sp aeec1300 error 4 in JLinkGDBServer[8048000+36000]
    Oct 11 13:35:52 ubuntu kernel: [371551.040183] JLinkGDBServer[24214]: segfault at ffffffff ip 08071121 sp af6f7240 error 5 in JLinkGDBServer[8048000+36000]

    /////////GDBServer launched again

    ERROR: Failed to bind address (Err = 98)
    ERROR: Failed to open listener port 2331


    *** J-Link GDB Server V4.78a Error ***
    Failed to open listener port. GDBServer will be closed.
    *** J-Link GDB Server V4.78a Error ***
    /var/log/syslog
    Oct 11 13:36:28 ubuntu USBBULK[24254]: *** J-Link GDB Server V4.78a
    Error *** | Failed to open listener port. GDBServer will be closed.


    I cannot provide more details about seg fault, the Valgrind is reports
    ==24299== More than 10000000 total errors detected. I'm not reporting any more.
    ==24299== Final error counts will be inaccurate. Go fix your program!
    ==24299== Rerun with --error-limit=no to disable this cutoff. Note
    ==24299== that errors may occur in your program without prior warning from
    ==24299== Valgrind, because errors are no longer being displayed.


    Best
    Martin
  • Hi Martin,

    Should already be done for most threads in GDBServer that are listening.
    Anyhow, we will check. We will also check regarding the seg fault you reported.
    Anything special we need to do not reproduce this seg fault?


    Best regards
    Alex
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/

    Or you can contact us via e-mail.
  • Hi,

    it happens sometimes (the seg fault), I cannot say exactly what steps are done.

    I can only post my configuration:
    uname -a : Linux ubuntu 3.2.0-54-generic-pae #82-Ubuntu SMP Tue Sep 10 20:29:22 UTC 2013 i686 i686 i386 GNU/Linux

    /etc/issue:Ubuntu 12.04.3 LTS \n \l

    arm-none-eabi-gdb -v: GNU gdb (Sourcery CodeBench 2013.05-53) 7.4.50.20120716-cvs

    Eclipse: Version: Juno Service Release 2, Build id: 20130225-0426
    Zylin Embedded CDT 4.18.1


    Best
    Martin