Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Xavier Roirand <roirand@adacore.com>
To: Simon Marchi <simon.marchi@polymtl.ca>
Cc: gdb-patches@sourceware.org, brobecker@adacore.com, tom@tromey.com
Subject: Re: [RFA 5/5 v3] Darwin: fix SIGTRAP when debugging
Date: Mon, 10 Sep 2018 15:31:00 -0000	[thread overview]
Message-ID: <6505460c-6a1c-4e5e-340f-b41b394defb6@adacore.com> (raw)
In-Reply-To: <26053bf8ea4ba887967ecc4747f94c2b@polymtl.ca>



Le 9/10/18 à 2:52 PM, Simon Marchi a écrit :
> On 2018-09-10 13:32, Xavier Roirand wrote:
>> Debugging a program under Darwin does not work:
>>
>> (gdb) start
>> Temporary breakpoint 1 at 0x100000fb4: file /tmp/helloworld.c, line 1.
>> Starting program: /private/tmp/helloworld
>> [New Thread 0x2903 of process 60326]
>> During startup program terminated with signal SIGTRAP, Trace/breakpoint
>> trap.
>>
>> Field signaled from darwin_thread_info is not initialized thus signal
>> sent to the debuggee is considered as not sent by GDB whereas it should.
>>
>> This patch fixes this problem and also updates (change type and/or
>> initialize) other fields in the same structure at the same time.
>>
>> gdb/ChangeLog:
>>
>>         * darwin-nat.h (struct darwin_thread_info) <gdb_port,
>>     inf_port, msg_state>: Initialize.
>>         (struct darwin_thread_info) <signaled, single_step>: Change
>>         type and initialize.
>>         (struct darwin_thread_info) <event>: Initialize.
>>
>> Change-Id: I0fe2a6985df9d0dfcc8a2a258a3ef70cfa19b403
>> ---
>>  gdb/darwin-nat.h | 12 ++++++------
>>  1 file changed, 6 insertions(+), 6 deletions(-)
>>
>> diff --git a/gdb/darwin-nat.h b/gdb/darwin-nat.h
>> index 5965df08ab6..89a7c06f6a1 100644
>> --- a/gdb/darwin-nat.h
>> +++ b/gdb/darwin-nat.h
>> @@ -114,25 +114,25 @@ enum darwin_msg_state
>>  struct darwin_thread_info : public private_thread_info
>>  {
>>    /* The thread port from a GDB point of view.  */
>> -  thread_t gdb_port;
>> +  thread_t gdb_port = 0;
>>
>>    /* The thread port from the inferior point of view.  Not to be used 
>> inside
>>       gdb except for get_ada_task_ptid.  */
>> -  thread_t inf_port;
>> +  thread_t inf_port = 0;
>>
>>    /* Current message state.
>>       If the kernel has sent a message it expects a reply and the 
>> inferior
>>       can't be killed before.  */
>> -  enum darwin_msg_state msg_state;
>> +  enum darwin_msg_state msg_state = DARWIN_RUNNING;
>>
>>    /* True if this thread is single-stepped.  */
>> -  unsigned char single_step;
>> +  bool single_step = false;
>>
>>    /* True if a signal was manually sent to the thread.  */
>> -  unsigned char signaled;
>> +  bool signaled = false;
>>
>>    /* The last exception received.  */
>> -  struct darwin_exception_msg event;
>> +  struct darwin_exception_msg event {};
>>  };
>>  typedef struct darwin_thread_info darwin_thread_t;
> 
> LGTM.  You do have push access I believe, is that right?

Yes, I do. I'll push it. Thanks.

> 
> Simon


  reply	other threads:[~2018-09-10 15:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 12:33 Xavier Roirand
2018-09-10 12:52 ` Simon Marchi
2018-09-10 15:31   ` Xavier Roirand [this message]
2018-09-11 13:40   ` Xavier Roirand

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=6505460c-6a1c-4e5e-340f-b41b394defb6@adacore.com \
    --to=roirand@adacore.com \
    --cc=brobecker@adacore.com \
    --cc=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tom@tromey.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