[Bug cli/16091] New: gdb seg faults on startup

[Bug cli/16091] New: gdb seg faults on startup

[gmc444 at yahoo dot com]

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

            Bug ID: 16091
           Summary: gdb seg faults on startup
           Product: gdb
           Version: 7.6
            Status: NEW
          Severity: normal
          Priority: P2
         Component: cli
          Assignee: unassigned at sourceware dot org
          Reporter: gmc444 at yahoo dot com

I built gdb 7.6.1 on Solaris 10 using gcc 4.8.1 with the following bash
commands:

CC="gcc -m64"
export CC
CXX="g++ -m64"
export CXX

MAKE=make
export MAKE

mkdir solx64
cd solx64
../configure -C --prefix=/home/gmc444/bin \
--exec-prefix=/home/gcompest/bin/solx64  --disable-tui
make
make install

On startup, it crashes immediately. pstack reports the following:

core 'core' of 20298:    ./gdb
 fffffd7fff0e6ce3 sem_invalid () + 3
 fffffd7ffef7715f PyThread_acquire_lock () + 37
 fffffd7ffef62451 new_threadstate () + c9
 fffffd7ffef6248a PyThreadState_New () + e
 fffffd7ffef62da6 PyGILState_Ensure () + 3e
 00000000005533c5 ensure_python_env () + 25
 0000000000554542 finish_python_initialization () + 22
 00000000005fd324 captured_main () + 594
 00000000005fb850 catch_errors () + 70
 00000000005fdcb4 gdb_main () + 24
 00000000007972b0 main () + 30
 00000000004f9d8c _start () + 6c

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

[Bug cli/16091] gdb seg faults on startup

[gmc444 at yahoo dot com]

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

gmc444 at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gmc444 at yahoo dot com

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

[Bug cli/16091] gdb seg faults on startup

[gmc444 at yahoo dot com]

http://sourceware.org/bugzilla/show_bug.cgi?id=16091

gmc444 at yahoo dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from gmc444 at yahoo dot com ---
I've been able to get beyond this problem by making several changes to my build
setup. Among them: using gmake instead of the default Solaris make, twiddling
with configure options, and running the build in the package's root directory.
I consider this resolved, though I wonder if there are safeguards that could be
put in place to catch problematic tools/setup at the configure stage.

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