Mac OS X JLinkGDBServer segfaults constantly

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

  • Mac OS X JLinkGDBServer segfaults constantly

    Log attached - this failure occurs for me 100% of the time when quitting the attached GDB session. After the error, subsequent attempts to attach hang forever; only unplugging & repluggin the JLink brings it back to life.

    Known bug? Workaround? Suggestions welcome!

    Source Code

    1. $ JLinkGDBServer -if SWD
    2. SEGGER J-Link GDB Server V4.78d
    3. JLinkARM.dll V4.78d (DLL compiled Oct 18 2013 19:20:06)
    4. The server has been started with the following settings:
    5. ---Server related settings---
    6. GDBInit file: none
    7. Listening port: 2331
    8. SWO thread listening port: 2332
    9. Semihosting TELNET port: 2333
    10. Accept remote connection: yes
    11. Logfile: off
    12. Verify download: off
    13. Init regs on start: on
    14. Silent mode: off
    15. Single run mode: off
    16. ---J-Link related settings---
    17. J-Link script: none
    18. Target interface: SWD
    19. Host interface: USB
    20. Target endian: little
    21. Target interface speed: 1000kHz
    22. Connecting to J-Link...
    23. J-Link is connected.
    24. Firmware: J-Link V9 compiled Oct 18 2013 17:37:30
    25. Hardware: V9.00
    26. S/N: 59102303
    27. Feature(s): GDB
    28. Checking target voltage...
    29. Listening on TCP/IP port 2331
    30. Connecting to target...Connected to target
    31. Waiting for GDB connection...Connected to 127.0.0.1
    32. Reading all registers
    33. Read 4 bytes @ address 0x00000000 (Data = 0x20008000)
    34. JTAG speed set to 1000 kHz
    35. Selecting device: TMPM342FYXBG
    36. SWO enabled succesfully.
    37. Flash breakpoints enabled
    38. Resetting target
    39. Downloading 512 bytes @ address 0x00000000
    40. Downloading 16240 bytes @ address 0x00010000
    41. Downloading 16288 bytes @ address 0x00013F70
    42. Downloading 16272 bytes @ address 0x00017F10
    43. Downloading 2656 bytes @ address 0x0001BEA0
    44. Downloading 1280 bytes @ address 0x0001C900
    45. Writing register (PC = 0x000126a1)
    46. Writing register (SP = 0x20008000)
    47. Writing register (PC = 0x000126A1)
    48. Read 4 bytes @ address 0x000126A0 (Data = 0xF240B5B0)
    49. Starting target CPU...
    50. Debugger requested to halt target...
    51. ...Target halted (PC = 0x00017476)
    52. Reading all registers
    53. Read 4 bytes @ address 0x00017476 (Data = 0x28006968)
    54. Read 2 bytes @ address 0x00017458 (Data = 0xB5B0)
    55. Read 2 bytes @ address 0x0001745A (Data = 0xF240)
    56. Read 2 bytes @ address 0x0001745C (Data = 0x6530)
    57. Read 2 bytes @ address 0x0001745E (Data = 0xAF02)
    58. Read 2 bytes @ address 0x00017460 (Data = 0xF2C2)
    59. Read 2 bytes @ address 0x00017462 (Data = 0x0500)
    60. Read 2 bytes @ address 0x00017464 (Data = 0xE007)
    61. Reading 64 bytes @ address 0x20003B80
    62. GDB closed TCP/IP connection
    63. Segmentation fault: 11
    Display All
  • Hi,

    We have already fixed this and plan to have a new version available until the end of this week.

    only unplugging & repluggin the JLink brings it back to life.

    We also implemented some modifications in the firmware that automatically reset & restart the J-Link after 5 seconds being in such a "hanging" state.


    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,

    Just had a look at it yesterday.
    The problem was hard to find, since it always appeared at another point and was timing dependent (and it never happened under Linux for an unknown reason...it should because the faulty code was also executed there)...
    New version is coming later this week.


    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.
  • Sorry for the delay...
    Fixed in V4.78h: segger.com/jlink-software.html


    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.