From: "nagaraju.m" <nagaraju.m@redpinesignals.com>
To: Paul Pluzhnikov <ppluzhnikov@google.com>
Cc: gdb@sourceware.org
Subject: Re: gdb script
Date: Fri, 24 Jul 2009 09:50:00 -0000 [thread overview]
Message-ID: <4A6983C1.7050705@redpinesignals.com> (raw)
In-Reply-To: <8ac60eac0907232339j6ba88e1cj8f620bf487775303@mail.gmail.com>
Paul,
I have given SIGTRAP signal but gdb is not giving control to
user, so I have changed to SIGINT and it is working.
Paul Pluzhnikov wrote:
> On Thu, Jul 23, 2009 at 11:15 PM,
> nagaraju.m<nagaraju.m@redpinesignals.com> wrote:
>
>
>> Paul, I have raised "SIGINT" signal in my target for hitting the breakpoint
>> is this signal causing the issue.
>>
>
> I have very little experience with embedded targets, and have
> absolutely no clue on how to interpret your statement above.
>
> But I think that yes, SIGINT may have something to do with the
> problem, as GDB is probably expecting SIGTRAP, not SIGINT.
>
>
prev parent reply other threads:[~2009-07-24 9:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-22 13:07 nagaraju.m
2009-07-22 21:30 ` Joel Brobecker
2009-07-23 0:34 ` Paul Pluzhnikov
2009-07-23 1:53 ` Joel Brobecker
2009-07-24 6:18 ` nagaraju.m
2009-07-24 6:39 ` Paul Pluzhnikov
2009-07-24 9:50 ` nagaraju.m [this message]
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=4A6983C1.7050705@redpinesignals.com \
--to=nagaraju.m@redpinesignals.com \
--cc=gdb@sourceware.org \
--cc=ppluzhnikov@google.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