From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gdb-prs-return-17349-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Received: (qmail 8813 invoked by alias); 22 Jan 2015 20:03:55 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Received: (qmail 8778 invoked by uid 55); 22 Jan 2015 20:03:53 -0000
From: "cvs-commit at gcc dot gnu.org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug threads/12074] multi-inferior internal error
Date: Thu, 22 Jan 2015 20:03:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: threads
X-Bugzilla-Version: HEAD
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: normal
X-Bugzilla-Who: cvs-commit at gcc dot gnu.org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-12074-4717-RxnYUUXkkP@http.sourceware.org/bugzilla/>
In-Reply-To: <bug-12074-4717@http.sourceware.org/bugzilla/>
References: <bug-12074-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2015-q1/txt/msg00114.txt.bz2

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

--- Comment #4 from cvs-commit at gcc dot gnu.org <cvs-commit at gcc dot gnu.org> ---
The master branch has been updated by Jan Kratochvil <jkratoch@sourceware.org>:

https://sourceware.org/git/gitweb.cgi?p=binutils-gdb.git;h=f0e8c4c5d1bce422ac86090b76c28931b0d240bf

commit f0e8c4c5d1bce422ac86090b76c28931b0d240bf
Author: Jan Kratochvil <jan.kratochvil@redhat.com>
Date:   Thu Jan 22 21:02:24 2015 +0100

    Print current thread after loading a core file

    downstream Fedora request:
        Please make it easier to find the backtrace of the crashing thread
        https://bugzilla.redhat.com/show_bug.cgi?id=1024504

    Currently after loading a core file GDB prints:

    Core was generated by `./threadcrash1'.
    Program terminated with signal SIGSEGV, Segmentation fault.
    8       *(volatile int *)0=0;
    (gdb) _

    there is nowhere seen which of the threads had crashed.  In reality GDB
always
    numbers that thread as #1 and it is the current thread that time.  But
after
    dumping all the info into a file for later analysis it is no longer
obvious.
    'thread apply all bt' even puts the thread #1 to the _end_ of the output!!!

    Should GDB always print after loading a core file what "thread" command
would
    print?
    [Current thread is 1 (Thread 0x7fcbe28fe700 (LWP 15453))]

    BTW I think it will print the thread even when loading single/non-threaded
    core file when other inferior(s) exist.  But that currently crashes
        [Bug threads/12074] multi-inferior internal error
        https://sourceware.org/bugzilla/show_bug.cgi?id=12074
    plus I think that would be a correct behavior anyway.

    gdb/ChangeLog
    2015-01-22  Jan Kratochvil  <jan.kratochvil@redhat.com>

        * corelow.c (core_open): Call also thread_command.
        * gdbthread.h (thread_command): New prototype moved from ...
        * thread.c (thread_command): ... here.
        (thread_command): Make it global.

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