From: Jon Ringle <jon@ringle.org>
To: Michael Snyder <Michael.Snyder@palmsource.com>
Cc: gdb@sourceware.org
Subject: Re: [SPAM] Re: gdbserver signals interfere with {next,step{,i}}
Date: Tue, 06 Mar 2007 02:40:00 -0000 [thread overview]
Message-ID: <45ECD480.9020901@ringle.org> (raw)
In-Reply-To: <1173147085.29183.61.camel@localhost.localdomain>
Michael Snyder wrote:
> OK, I built it with arm-linux-gcc -lrt -lpthread -g
>
> I copied it to my arm dev board running kernel 2.6.14
> (intel Zylonite)
>
> I started it under gdbserver 6.5, connected to it with gdb 6.5,
> break on line 106 as suggested by the comment, gave it some
> input, hit the breakpoint, nexted a few times...
>
> I didn't see any odd behavior (I also didn't see gdb report any
> SIGUSR1 events).
>
>
Did you do a 'handle SIGUSR1 nostop noprint' to avoid seeing SIGUSR1 events?
Did the "Prompt %d" increment as you proceeded with the test?
Other details about my target: linux 2.6.16.29, uclibc-0.9.28, gdbserver
6.6, gdb 6.6, armeb-linux-gcc 3.4.6
Jon
next prev parent reply other threads:[~2007-03-06 2:40 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 20:06 Jon Ringle
2007-03-05 20:17 ` Daniel Jacobowitz
2007-03-05 23:20 ` Jon Ringle
2007-03-06 1:43 ` Michael Snyder
2007-03-06 1:48 ` [SPAM] " Jon Ringle
2007-03-06 2:11 ` Michael Snyder
2007-03-06 2:25 ` [SPAM] " Jon Ringle
2007-03-06 12:25 ` Daniel Jacobowitz
2007-03-06 14:31 ` Jon Ringle
2007-03-06 14:39 ` Daniel Jacobowitz
2007-03-06 14:57 ` Jon Ringle
2007-03-06 19:46 ` Michael Snyder
2007-03-06 20:18 ` Jon Ringle
2007-03-06 20:19 ` Daniel Jacobowitz
2007-03-06 19:41 ` Michael Snyder
2007-03-06 20:10 ` Jon Ringle
2007-03-06 2:40 ` Jon Ringle [this message]
2007-03-06 5:07 ` Jon Ringle
2007-03-06 1:17 ` Michael Snyder
2007-03-06 1:30 ` Jon Ringle
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=45ECD480.9020901@ringle.org \
--to=jon@ringle.org \
--cc=Michael.Snyder@palmsource.com \
--cc=gdb@sourceware.org \
/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