Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Ulisses Furquim" <ulissesf@gmail.com>
To: gdb@sourceware.org
Cc: "Ulisses Furquim" <ulissesf@gmail.com>
Subject: Re: Problems with multi-threaded application debugging
Date: Thu, 31 May 2007 18:35:00 -0000	[thread overview]
Message-ID: <d23110170705311135g3fad2604ja74e4455e4cfe1d8@mail.gmail.com> (raw)
In-Reply-To: <20070531170448.GB23197@localhost.localdomain>

Hi Daniel,

On 5/31/07, Daniel Jacobowitz <drow@false.org> wrote:
> > - sometimes when you "continue" gdb doesn't stop at a breakpoint
> > inside some of the threads;
> > - sometimes when you try to single step (with "next") all the threads
> > run until the program exits;
>
> I have no idea what these might be.

Yeah, I thought it was really strange and I can trigger this behavior
with a really simple application.

> > - I was trying to use the scheduler-locking variable (setting it to
> > "on"), but it seems I can single step on only one thread. I mean, If I
> > switch to another thread and try to single step it, gdb switches back
> > to the previous thread.
>
> To be honest, I can't completely remember whether this is supposed to
> happen still or supposed to be fixed.  You need to be using a current
> version of gdb and gdbserver, but GDB may still be doing something
> wrong.

Ah, I'm sorry, I wasn't completely clear. I forgot to say that I can
trigger all those problems with gdb 6.4-debian (from Ubuntu Edgy) on a
x86 machine and also with gdb 6.6 on an ARM device. I'm not even using
gdbserver (yet).

Regards,

-- Ulisses


      reply	other threads:[~2007-05-31 18:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 12:50 Ulisses Furquim
2007-05-31 17:23 ` Daniel Jacobowitz
2007-05-31 18:35   ` Ulisses Furquim [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=d23110170705311135g3fad2604ja74e4455e4cfe1d8@mail.gmail.com \
    --to=ulissesf@gmail.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