public inbox for gdb-prs@sourceware.org
help / color / mirror / Atom feed
From: "simon.marchi at ericsson dot com" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug server/17302] gdbserver function call + detach crashes inferior process
Date: Wed, 03 Sep 2014 15:51:00 -0000	[thread overview]
Message-ID: <bug-17302-4717-FN99mH6dC8@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-17302-4717@http.sourceware.org/bugzilla/>

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

--- Comment #2 from Simon Marchi <simon.marchi at ericsson dot com> ---
I found that during the manual call to a function by gdbserver, a segmentation
fault/SIGSEGV is generated. When detaching, gdbserver delivers the pending
SIGSEGV, causing the crash of the detached process.

When preparing the inferior call, gdb starts by expanding a stack a bit. It
then places a breakpoint instruction (0xCC) somewhere in that area. It then
prepares the dummy frame, including writing the return address, which is the
address where the 0xCC is. So when the function ends, execution should go where
the breakpoint and it should stop. However, since stack is generally not
executable, when the processor tries to "execute" the breakpoint instruction, a
segmentation fault/SIGSEGV is generated instead of the normal SIGTRAP.

When making the stack executable, the problem disappears, so I am quite
confident that this is the reason. In order to make the stack executable, I use
execstack (it modifies a flag in the binary):

$ execstack -s binary

I have no idea why this only happens in gdbserver, and not in gdb.

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


  parent reply	other threads:[~2014-09-03 15:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 13:26 [Bug server/17302] New: " simon.marchi at ericsson dot com
2014-08-22 13:28 ` [Bug server/17302] " simon.marchi at ericsson dot com
2014-09-03 15:51 ` simon.marchi at ericsson dot com [this message]
2014-09-03 15:51 ` simon.marchi at ericsson dot com
2014-09-03 18:25 ` simon.marchi at ericsson dot com
2014-12-10 21:14 ` cvs-commit at gcc dot gnu.org

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-17302-4717-FN99mH6dC8@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).