Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@false.org>
To: Milrith <milrith@gmail.com>
Cc: gdb@sourceware.org
Subject: Re: Problems with remote debugging on ARM
Date: Tue, 16 May 2006 19:49:00 -0000	[thread overview]
Message-ID: <20060516190439.GA10663@nevyn.them.org> (raw)
In-Reply-To: <20060516205958.beae8e7b.milrith@gmail.com>

On Tue, May 16, 2006 at 08:59:58PM +0200, Milrith wrote:
> Yes, I am using gdbserver. Right now SIGALRM is treated as pass noprint
> nostop. Would you have more details on how to do this hack? ;)

Look in gdbserver/linux-low.c for SIGRTMIN.

> > > I have problems with breakpoints not taken into account, are there
> > > known problems with some parts of my configuration (C++ or threads)?
> > 
> > Are they in constructors?  Google would be glad to tell you about the
> > problem, in that case.
> 
> Unfortunately not, it can happen in normal methods. I am compiling
> with -g and without any optimisation option.

Then we'll need you to submit a test case.

> Another little problem: I can't autocomplete method names with "::"
> after the class names (Class::<tab> produces nothing), I suppose I am
> missing a little something?

Try putting a single quote beforehand:

  print 'Class::<tab>

That'll work for now.

-- 
Daniel Jacobowitz
CodeSourcery


      reply	other threads:[~2006-05-16 19:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-16 18:18 Milrith
2006-05-16 18:25 ` Daniel Jacobowitz
2006-05-16 19:03   ` Mark Kettenis
2006-05-16 19:05     ` Daniel Jacobowitz
2006-05-16 19:25   ` Milrith
2006-05-16 19:49     ` Daniel Jacobowitz [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=20060516190439.GA10663@nevyn.them.org \
    --to=drow@false.org \
    --cc=gdb@sourceware.org \
    --cc=milrith@gmail.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