This is the mail archive of the gdb-prs@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug tui/13422] New: Segmentation fault due to lack of tui setup


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

             Bug #: 13422
           Summary: Segmentation fault due to lack of tui setup
           Product: gdb
           Version: unknown
            Status: NEW
          Severity: normal
          Priority: P2
         Component: tui
        AssignedTo: unassigned@sourceware.org
        ReportedBy: sphink@gmail.com
    Classification: Unclassified


I have a script that starts up gdb inside of emacs from the command line, and
it began seg faulting on startup after updating gdb.

I can't remember how I managed to catch this in the debugger (it involved a
weird timing hack), but I can reproduce this with just the command line

  emacs --eval '(gdb "/home/sfink/src/archer/gdb/gdb --annotate=3
/usr/bin/flac")'

where /usr/bin/flac can be any binary for which debug info is available.
Switching to a binary with no debug info will eliminate the crash, as will
removing the --annotate=3. The crash is a NULL pointer dereference on some tui
data structure.

Reverting commit edde6978a5c3ee8a2eeafa99a13a6ecb95bf1aff fixes the problem for
me.

-- 
Configure bugmail: http://sourceware.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]