From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: gdb-patches <gdb-patches@sourceware.org>
Subject: [patch] Print current thread after loading a core file [Re: [patch] Sort threads for thread apply all (bt)]
Date: Sat, 17 Jan 2015 20:59:00 -0000 [thread overview]
Message-ID: <20150117205934.GA31682@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22R_dY8nfU4bgpPS+4K5gG9cdMzCqW--H85hMwBDdh+MRg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 851 bytes --]
On Thu, 15 Jan 2015 20:29:07 +0100, Doug Evans wrote:
> On Thu, Jan 15, 2015 at 10:33 AM, Jan Kratochvil <jan.kratochvil@redhat.com> wrote:
> > Should GDB always print after loading a core file what "thread" command would
> > print?
> > [Current thread is 1 (Thread 0x7fcbe28fe700 (LWP 15453))]
>
> Sounds reasonable to me.
> Though there is the concern to not even talk about threads if there are "none".
> So maybe only print that if there is more than one thread?
Attached.
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.
No regressions on {x86_64,x86_64-m32}-fedora22pre-linux-gnu.
Jan
[-- Attachment #2: corethreads2.patch --]
[-- Type: text/plain, Size: 2112 bytes --]
gdb/ChangeLog
2015-01-17 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.
diff --git a/gdb/corelow.c b/gdb/corelow.c
index a9eadd5..c168d1a 100644
--- a/gdb/corelow.c
+++ b/gdb/corelow.c
@@ -456,6 +456,17 @@ core_open (const char *arg, int from_tty)
/* Now, set up the frame cache, and print the top of stack. */
reinit_frame_cache ();
print_stack_frame (get_selected_frame (NULL), 1, SRC_AND_LOC, 1);
+
+ /* Current thread should be NUM 1 but the user does not know that. */
+ if (thread_count () >= 2)
+ {
+ TRY_CATCH (except, RETURN_MASK_ERROR)
+ {
+ thread_command (NULL, from_tty);
+ }
+ if (except.reason < 0)
+ exception_print (gdb_stderr, except);
+ }
}
static void
diff --git a/gdb/gdbthread.h b/gdb/gdbthread.h
index 15a979b..a2f378a 100644
--- a/gdb/gdbthread.h
+++ b/gdb/gdbthread.h
@@ -455,6 +455,8 @@ extern void finish_thread_state_cleanup (void *ptid_p);
/* Commands with a prefix of `thread'. */
extern struct cmd_list_element *thread_cmd_list;
+extern void thread_command (char *tidstr, int from_tty);
+
/* Print notices on thread events (attach, detach, etc.), set with
`set print thread-events'. */
extern int print_thread_events;
diff --git a/gdb/thread.c b/gdb/thread.c
index ed20fbe..4bce212 100644
--- a/gdb/thread.c
+++ b/gdb/thread.c
@@ -62,7 +62,6 @@ static int highest_thread_num;
spawned new threads we haven't heard of yet. */
static int threads_executing;
-static void thread_command (char *tidstr, int from_tty);
static void thread_apply_all_command (char *, int);
static int thread_alive (struct thread_info *);
static void info_threads_command (char *, int);
@@ -1506,7 +1505,7 @@ thread_apply_command (char *tidlist, int from_tty)
/* Switch to the specified thread. Will dispatch off to thread_apply_command
if prefix of arg is `apply'. */
-static void
+void
thread_command (char *tidstr, int from_tty)
{
if (!tidstr)
next prev parent reply other threads:[~2015-01-17 20:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-15 18:33 [patch] Sort threads for thread apply all (bt) Jan Kratochvil
2015-01-15 19:29 ` Doug Evans
2015-01-16 23:38 ` [patchv2] " Jan Kratochvil
2015-01-22 0:26 ` Doug Evans
2015-01-22 11:18 ` Pedro Alves
2015-01-22 16:43 ` Jan Kratochvil
2015-01-22 17:07 ` Pedro Alves
2015-01-22 17:18 ` Jan Kratochvil
2015-01-22 18:09 ` Doug Evans
2015-01-22 18:13 ` Jan Kratochvil
2015-01-22 18:49 ` [patchv3] " Jan Kratochvil
2015-01-22 18:52 ` Eli Zaretskii
2015-01-22 19:24 ` [patchv4] " Jan Kratochvil
2015-01-22 19:34 ` Doug Evans
2015-01-22 20:08 ` Doug Evans
2015-01-22 21:15 ` [commit] [patchv5] " Jan Kratochvil
2015-01-22 20:52 ` [patchv4] " Eli Zaretskii
2015-01-22 19:10 ` [patchv3] " Doug Evans
2015-01-22 19:23 ` Doug Evans
2015-01-22 19:24 ` [patchv5] " Jan Kratochvil
2015-01-22 20:37 ` [patchv3] " Doug Evans
2015-01-17 20:59 ` Jan Kratochvil [this message]
2015-01-22 0:36 ` [patch] Print current thread after loading a core file [Re: [patch] Sort threads for thread apply all (bt)] Doug Evans
2015-01-22 18:36 ` [commit] " Jan Kratochvil
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=20150117205934.GA31682@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=dje@google.com \
--cc=gdb-patches@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).