Re: breakpoints/1407: Gdb with gcc on Solaris crashes withsegmentation fault when using "call"

[Mark Kettenis <kettenis at chello dot nl>]

The following reply was made to PR breakpoints/1407; it has been noted by GNATS.

From: Mark Kettenis <kettenis@chello.nl>
To: blocke@newpaltz.edu
Cc: gdb-gnats@sources.redhat.com
Subject: Re: breakpoints/1407: Gdb with gcc on Solaris crashes with
	segmentation fault when using "call"
Date: Sat, 11 Oct 2003 15:19:37 +0200 (CEST)

    From: "Bruce A. Locke" <blocke@newpaltz.edu>
    Date: 09 Oct 2003 17:55:57 -0400
 
    In reference to bug #1407 in gdb-gnats:
 
    I pulled the CVS branch as specified in a response to the original bug
    report and it does not appear to fix the problem.
 
    Any input you could offer would be appreciated.  Thank You.
 
 Works fine here (Solaris 2.6, gcc 3.3.2).  Wait a moment...
 
 ...does your Solaris system have a non-executable stack?  If I set:
 
 $ tail /etc/system
 *
 *       To set variables in 'unix':
 *
 *               set nautopush=32
 *               set maxusers=40
 *
 *       To set a variable named 'debug' in the module named 'test_module'
 *
 *               set test_module:debug = 0x13
 set noexec_user_stack = 1
 
 I see the same segfaults as you're seeing.  Right now calling
 functions from GDB requires the execution of a bit of code on the
 stack.  We have some ideas to fix this, but it's not a simple problem
 to fix.
 
 For now the only thing I can advice you is to make the stack
 executable, or find another machine that doesn't have a non-executable
 stack.
 
 Mark