From: Yao Qi <yao@codesourcery.com>
To: Marc Khouzam <marc.khouzam@ericsson.com>
Cc: "'gdb-patches@sourceware.org'" <gdb-patches@sourceware.org>
Subject: Re: [PATCH 0/2] Create inferior fro trace file target
Date: Wed, 05 Feb 2014 12:54:00 -0000 [thread overview]
Message-ID: <52F2340F.5010909@codesourcery.com> (raw)
In-Reply-To: <E59706EF8DB1D147B15BECA3322E4BDC1C57CE2C@eusaamb103.ericsson.se>
On 01/31/2014 03:21 AM, Marc Khouzam wrote:
> When starting the debug session, for a user, it is very similar to ask
> to look at a core file than to look at a trace file. So in Eclipse, it is
> the same UI except that the user specifies if the file is a trace file
> or a core file.
>
Hmmm, that makes sense to me.
>> > These two patches bring an issue for multi-target support, say if GDB opens
>> > two trace files in two targets, what is the expected output of "info inferiors"
>> > and "info threads"?
> If you are asking about Eclipse, we don't support multi-target, so the problem
> never presented itself. Maybe this should be part of a bigger discussion about
> how trace files should be handled.
I meant these patches bring potential problems to multi-target
transition. We (GDB folks) will revisit them when we go there.
>
>> > *** BLURB HERE ***
> (Out of curiosity, I've wondered why you have the above line in your patch posts.)
>
It is part of the cover letter of this patch series, generated by
'git format-patch --cover-letter'.
--
Yao (é½å°§)
next prev parent reply other threads:[~2014-02-05 12:54 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 [this message]
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
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=52F2340F.5010909@codesourcery.com \
--to=yao@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=marc.khouzam@ericsson.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