From: David Griffiths <dgriffiths@undo.io>
To: Pedro Alves <palves@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: "finish" command leads to SIGTRAP
Date: Thu, 21 Feb 2019 12:13:00 -0000 [thread overview]
Message-ID: <CA++j6c4co2Uz=3q952pf3skq8xMdsmQ_4+H6eMBkAdvyXMzK8A@mail.gmail.com> (raw)
In-Reply-To: <b437759f-5223-fcd2-1e68-f77051a2f910@redhat.com>
Ok thanks, did that. If I compare the output for the bad case with the good
case, this seems to be the main difference:
< infrun: proceed: resuming Thread 0x7ffff7fd8700 (LWP 12901)
< infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current
thread [Thread 0x7ffff7fd8700 (LWP 12901)] at 0x7ffff6d33b00
< LLR: Preparing to resume Thread 0x7ffff7fd8700 (LWP 12901), 0,
inferior_ptid Thread 0x7ffff7fd8700 (LWP 12901)
< LLR: PTRACE_CONT Thread 0x7ffff7fd8700 (LWP 12901), 0 (resume event
thread)
---
> infrun: step-over queue now empty
> infrun: resuming [Thread 0x7ffff7fd8700 (LWP 12901)] for step-over
> infrun: resume (step=1, signal=GDB_SIGNAL_0), trap_expected=1, current
thread [Thread 0x7ffff7fd8700 (LWP 12901)] at 0x7ffff6d33b00
> LLR: Preparing to step Thread 0x7ffff7fd8700 (LWP 12901), 0,
inferior_ptid Thread 0x7ffff7fd8700 (LWP 12901)
> LLR: PTRACE_SINGLESTEP Thread 0x7ffff7fd8700 (LWP 12901), 0 (resume event
thread)
10a11
> infrun: proceed: [Thread 0x7ffff7fd8700 (LWP 12901)] resumed
27c28,60
< infrun: random signal (GDB_SIGNAL_TRAP)
---
> infrun: no stepping, continue
> infrun: resume (step=0, signal=GDB_SIGNAL_0), trap_expected=0, current
thread [Thread 0x7ffff7fd8700 (LWP 12901)] at 0x7ffff6d33b01
Cheers,
David
On Thu, 21 Feb 2019 at 11:24, Pedro Alves <palves@redhat.com> wrote:
> On 02/21/2019 11:21 AM, David Griffiths wrote:
> >
> > I need it to work because I'm trying to automate something via gdb/MI.
> Any
> > suggestions as to how to debug this would be very welcome.
>
> Start with "set debug infrun 1".
>
> And then "set debug lin-lwp 1" if debugging natively, or
> "set debug remote 1" if using the remote serial protocol.
>
> Thanks,
> Pedro Alves
>
--
David Griffiths, Senior Software Engineer
Undo <https://undo.io> | Resolve even the most challenging software defects
with software flight recorder technology
Software reliability report: optimizing the software supplier and customer
relationship
<https://info.undo.io/software-reliability-report-optimizing-supplier-and-customer-relationship>
next prev parent reply other threads:[~2019-02-21 12:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 11:21 David Griffiths
2019-02-21 11:24 ` Pedro Alves
2019-02-21 12:13 ` David Griffiths [this message]
2019-02-21 12:17 ` David Griffiths
2019-02-21 13:12 ` Pedro Alves
2019-02-21 15:55 ` David Griffiths
2019-02-21 17:50 ` Pedro Alves
2019-02-21 18:03 ` Pedro Alves
2019-02-21 18:22 ` David Griffiths
2019-02-21 18:50 ` John Baldwin
2019-02-21 19:34 ` Pedro Alves
2019-02-21 20:50 ` John Baldwin
2019-02-22 15:09 ` Pedro Alves
2019-02-22 16:42 ` John Baldwin
2019-02-22 17:38 ` David Griffiths
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='CA++j6c4co2Uz=3q952pf3skq8xMdsmQ_4+H6eMBkAdvyXMzK8A@mail.gmail.com' \
--to=dgriffiths@undo.io \
--cc=gdb@sourceware.org \
--cc=palves@redhat.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