Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <Michael.Snyder@palmsource.com>
To: Jon Ringle <jon@ringle.org>
Cc: gdb@sourceware.org
Subject: Re: gdbserver signals interfere with {next,step{,i}}
Date: Tue, 06 Mar 2007 02:11:00 -0000	[thread overview]
Message-ID: <1173147085.29183.61.camel@localhost.localdomain> (raw)
In-Reply-To: <45ECC84A.9020702@ringle.org>

On Mon, 2007-03-05 at 20:47 -0500, Jon Ringle wrote:
> Michael Snyder wrote:
> >>> Attached is a test case. 
> >>>       
> >
> > What library do I link to for timer_create?
> >
> >
> >   
> This is how I built the testcase:
> $ CC=armeb-linux-gcc LDFLAGS="-lrt -lpthread" CFLAGS="-g" make 
> gdbsignal-test

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).


  reply	other threads:[~2007-03-06  2:11 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 [this message]
2007-03-06  2:25           ` 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
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=1173147085.29183.61.camel@localhost.localdomain \
    --to=michael.snyder@palmsource.com \
    --cc=gdb@sourceware.org \
    --cc=jon@ringle.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