Reproducible error

Sysprogs forums › Forums › VisualGDB › Reproducible error

Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • August 5, 2014 at 15:14 #810
    Anonymous
    Participant

    I am debugging software which makes use of fork(). It is possible to get debugging into a frozen state where neither the continue or break buttons are available (and the program continues execution).

    Steps to reproduce:

    1. Break All
    2. Change threads with “inferior 2”
    3. Break All

    This break all never completes, and for this software which contains three forks it is necessary. This is reproducible 100% of the time.

    root@splitice-VirtualBox:~# gdb -v
GNU gdb (Ubuntu 7.7-0ubuntu3.1) 7.7
Copyright (C) 2014 Free Software Foundation, Inc.
    August 5, 2014 at 20:37 #3138
    support
    Keymaster

    Hi,

    From a quick look this looks more like a GDB issue. The ‘break all’ simply sends a Ctrl-C event to GDB. You can try experimenting with the set follow-fork-mode command or go to the Custom Debug steps page of VisualGDB Project Properties and override the ‘Break All’ action with a ‘killall -s INT ‘ command to send a SIGINT to all instances you’re debugging.

  • Author
    Posts
Log In Register Lost Password
Viewing 2 posts - 1 through 2 (of 2 total)
  • You must be logged in to reply to this topic.