From: Tom Tromey <tromey@redhat.com>
To: Pedro Alves <pedro@codesourcery.com>
Cc: gdb-patches@sourceware.org, Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: RFC: lazily call save_current_space_and_thread
Date: Tue, 08 Mar 2011 20:01:00 -0000 [thread overview]
Message-ID: <m34o7dgzgo.fsf@fleche.redhat.com> (raw)
In-Reply-To: <201103081802.35770.pedro@codesourcery.com> (Pedro Alves's message of "Tue, 8 Mar 2011 18:02:35 +0000")
>>>>> "Pedro" == Pedro Alves <pedro@codesourcery.com> writes:
Pedro> Okay. In any case, what I was aluding to, is that
Pedro> in non-stop mode gdb is making sure the user selected
Pedro> frame is constant between events (fetch_inferior_event),
Pedro> so in that case, there's a selected frame to restore back
Pedro> to. But thinking a bit more, that obviously doesn't matter
Pedro> because if the user had a frame selected, then the debug info
Pedro> for that frame has already been read anyway, and there's nothing
Pedro> to optimize.
Also, this code will still do the right thing if there actually is a
selected frame.
Moving the selected frame to be per-thread would also help here.
But I am going to guess that this is tricky, for the same reasons that
making the regcache per-thread is tricky.
Pedro> Error in re-setting breakpoint 1: Cannot access memory at address 0x45e22a
Pedro> Error in re-setting breakpoint 2: Cannot access memory at address 0x4e2e5a
Pedro> warning: Error removing breakpoint 1
Pedro> warning: Error removing breakpoint 2
I didn't run into this, but I have seen other weird things, like errors
from libpthread_db. I haven't investigated yet.
Tom
next prev parent reply other threads:[~2011-03-08 19:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-04 19:52 Tom Tromey
2011-03-05 12:52 ` Jan Kratochvil
2011-03-07 19:54 ` Tom Tromey
2011-03-08 17:14 ` Tom Tromey
2011-03-08 17:16 ` Jan Kratochvil
2011-03-08 17:23 ` Pedro Alves
2011-03-08 17:49 ` Tom Tromey
2011-03-08 17:56 ` Pedro Alves
2011-03-08 18:02 ` Tom Tromey
2011-03-08 18:15 ` Pedro Alves
2011-03-08 18:37 ` Pedro Alves
2011-03-08 20:01 ` Tom Tromey [this message]
2011-03-08 23:02 ` Pedro Alves
2011-03-10 20:09 ` Tom Tromey
2011-03-08 19:54 ` Tom Tromey
2011-03-08 19:54 ` Pedro Alves
2011-03-09 14:43 ` Tom Tromey
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=m34o7dgzgo.fsf@fleche.redhat.com \
--to=tromey@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=pedro@codesourcery.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