From: Pedro Alves <palves@redhat.com>
To: Yao Qi <yao@codesourcery.com>
Cc: gdb-patches@sourceware.org, marc.khouzam@ericsson.com
Subject: Re: [PATCH 0/2] Create inferior fro trace file target
Date: Wed, 05 Feb 2014 12:31:00 -0000 [thread overview]
Message-ID: <52F22F0C.9010901@redhat.com> (raw)
In-Reply-To: <52F22B49.2050802@codesourcery.com>
On 02/05/2014 12:15 PM, Yao Qi wrote:
>> > We've moved in the direction of "always a thread" a while ago,
> What is "always a thread"? Can you elaborate?
"info threads" used to come out empty until a second thread
showed up.
Here's 6.8 debugging a single-threaded program:
(gdb) info threads
(gdb) info program
Using the running image of child process 12775.
Program stopped at 0x4004cf.
It stopped at a breakpoint that has since been deleted.
(gdb)
vs 7.0/current mainline:
(gdb) info threads
Id Target Id Frame
* 1 process 12748 "main" main (argc=1, argv=0x7fffffffdb18) at main.c:5
(gdb)
Basically, GDB nowadays models non-threaded programs as single-threaded
programs. Thus "always a(t least one) thread".
--
Pedro Alves
next prev parent reply other threads:[~2014-02-05 12:31 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-30 5:46 Yao Qi
2014-01-30 5:46 ` [PATCH 1/2] Create inferior for tfile target Yao Qi
2014-01-30 5:47 ` [PATCH 2/2] Create inferior for ctf target Yao Qi
2014-01-30 19:21 ` [PATCH 0/2] Create inferior fro trace file target Marc Khouzam
2014-02-05 12:54 ` Yao Qi
2014-02-04 20:57 ` Pedro Alves
2014-02-04 21:08 ` Marc Khouzam
2014-02-04 21:17 ` Pedro Alves
2014-02-05 2:05 ` Joel Brobecker
2014-02-05 12:17 ` Yao Qi
2014-02-05 12:24 ` Joel Brobecker
2014-02-05 12:31 ` Pedro Alves [this message]
2014-02-05 12:42 ` Mark Kettenis
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=52F22F0C.9010901@redhat.com \
--to=palves@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.com \
--cc=yao@codesourcery.com \
/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