This is the mail archive of the
gdb-patches@sourceware.org
mailing list for the GDB project.
Re: [PATCH] gdbserver: Fix crash when QTinit is handled with no inferior process attached
- From: Pedro Alves <palves at redhat dot com>
- To: Antoine Tremblay <antoine dot tremblay at ericsson dot com>, lgustavo at codesourcery dot com, gdb-patches at sourceware dot org
- Date: Thu, 05 Feb 2015 18:35:55 +0100
- Subject: Re: [PATCH] gdbserver: Fix crash when QTinit is handled with no inferior process attached
- Authentication-results: sourceware.org; auth=none
- References: <1422387337-32334-1-git-send-email-antoine dot tremblay at ericsson dot com> <54D37065 dot 4020303 at ericsson dot com> <54D37228 dot 2000309 at codesourcery dot com> <54D373C3 dot 5040201 at codesourcery dot com> <54D375DD dot 5090704 at ericsson dot com> <54D3787A dot 60605 at codesourcery dot com> <54D378FA dot 1090809 at ericsson dot com>
Agreed with both. :-)
On the test, I think it could go under gdb.trace/, and not use
any of gdbserver_start_extended and friends. That'd expose the
use case to all targets that can do tracing. gdbserver's case
would be covered by running the testsuite with the
extended-remote board, which is now routinely run by the
GDB's Buildbot (https://sourceware.org/ml/gdb-testers/2015-q1/).
WDYT?
Thanks,
Pedro Alves