Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change the behaviour of core::run::Program.destroy to forcibly terminate the program #5761

Closed
wants to merge 4 commits into from

Commits on Apr 6, 2013

  1. Fix a bug where calling p.destroy() on the result of calling

    start_program(...) would cause a segfault when p went
    out of scope due to out_file/err_file being closed twice.
    gareth authored and gareth committed Apr 6, 2013
    Configuration menu
    Copy the full SHA
    e081c17 View commit details
    Browse the repository at this point in the history
  2. Update doc-comments to reflect the current year and trait

    names now being capitalized.
    gareth authored and gareth committed Apr 6, 2013
    Configuration menu
    Copy the full SHA
    622bb63 View commit details
    Browse the repository at this point in the history
  3. Change the behaviour of core::run::Program.destroy to

    forcibly terminate the program (as suggested in issue rust-lang#5632)
    gareth authored and gareth committed Apr 6, 2013
    Configuration menu
    Copy the full SHA
    483e95a View commit details
    Browse the repository at this point in the history

Commits on Apr 11, 2013

  1. Make destroy() send SIGTERM and add a new method called

    force_destroy() that sends SIGKILL - as suggested by 
    @thestinger.
    gareth authored and gareth committed Apr 11, 2013
    5 Configuration menu
    Copy the full SHA
    995d444 View commit details
    Browse the repository at this point in the history