This is the mail archive of the gdb-patches@sourceware.org mailing list for the GDB project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: RFC: lazily call save_current_space_and_thread


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


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]