public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "a.c.kalker at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/18405] New: Running gdbserver with nonexistent debuggee throws assertion
Date: Tue, 12 May 2015 20:04:00 -0000	[thread overview]
Message-ID: <bug-18405-4717@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=18405

            Bug ID: 18405
           Summary: Running gdbserver with nonexistent debuggee throws
                    assertion
           Product: gdb
           Version: 7.9
            Status: NEW
          Severity: normal
          Priority: P2
         Component: server
          Assignee: unassigned at sourceware dot org
          Reporter: a.c.kalker at gmail dot com
  Target Milestone: ---

Using Arch Linux x86_64, package gdb 7.9-1 from its official repositories.

Steps to reproduce:

- Run gdbserver on a non-existent debuggee

Actual results:

$ gdbserver localhost:1234 doesnotexist
Process doesnotexist created; pid = 9065
Cannot exec doesnotexist: No such file or directory.

Child exited with status 127
Killing process(es): 9065
linux-low.c:969: A problem internal to GDBserver has been detected.
kill_wait_lwp: Assertion `res > 0' failed.
$

Expected results:

- gdbserver should just report that the file does not exist and then exit
normally.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


             reply	other threads:[~2015-05-12 20:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-12 20:04 a.c.kalker at gmail dot com [this message]
2015-05-13  9:25 ` [Bug server/18405] " palves at redhat dot com
2015-05-13 14:49 ` a.c.kalker at gmail dot com

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-18405-4717@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=gdb-prs@sourceware.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).