From: Pedro Alves <pedro@codesourcery.com>
To: gdb-patches@sourceware.org
Cc: Tom Tromey <tromey@redhat.com>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: RFC: lazily call save_current_space_and_thread
Date: Tue, 08 Mar 2011 18:37:00 -0000 [thread overview]
Message-ID: <201103081815.25814.pedro@codesourcery.com> (raw)
In-Reply-To: <201103081802.35770.pedro@codesourcery.com>
On Tuesday 08 March 2011 18:02:35, Pedro Alves wrote:
> I suspect it's related to spawning iconv (or rather, that's
> triggering some bug).
Err, I must have blown a fuse or something. That example
was me running gdb under gdb, and doing "run", with the
options you posted. Naturaly, the inferior gdb is spawning
iconv, and the superior gdb catches that. That is triggering
some bug, which may not even be what you're seeing, but
it's most likely irrevelant _what_ does the inferior spawn,
as long as it spawns something. Errors accessing memory
like in my previous post are usually caused by gdb
reading/writing to/from the wrong process..
--
Pedro Alves
next prev parent reply other threads:[~2011-03-08 18:15 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 [this message]
2011-03-08 20:01 ` Tom Tromey
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=201103081815.25814.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=tromey@redhat.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