From: Jeremy Fitzhardinge <jeremy@goop.org>
To: walt <w41ter@gmail.com>
Cc: linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>,
Andi Kleen <ak@muc.de>
Subject: Re: 2.6.19-rc6-mm2 hangs when gdb is run on a multithread program
Date: Sun, 10 Dec 2006 17:45:32 -0800 [thread overview]
Message-ID: <457CB83C.5060107@goop.org> (raw)
In-Reply-To: <457CB4A6.5090807@gmail.com>
walt wrote:
> Jeremy Fitzhardinge wrote:
>
>> Pedro Larroy Tovar wrote:
>>
>>> Hi
>>>
>>> I can reproduce a crash with 2.6.19-rc6-mm2 triggered when debugging a
>>> program with gdb that uses pthreads. No oops or anything strange seems
>>> to be printed by the kernel, but the box appears to stop doing disk IO.
>>>
>
>
>> Hm, I wonder if this is related walt's problem running things under gdb?
>>
>
> Jeremy, I redid my git-bisect from scratch and came up with a different
> commit for the gdb breakage:
>
> commit f95d47caae5302a63d92be9a0292abc90e2a14e1
> Author: Jeremy Fitzhardinge <jeremy@goop.org>
> Date: Thu Dec 7 02:14:02 2006 +0100
> [PATCH] i386: Use %gs as the PDA base-segment in the kernel
>
> This commit is the one which causes gdb to halt with this error
> no matter what executable I try to run:
> Warning:
> Cannot insert breakpoint -2.
> Error accessing memory address 0xd74b: Input/output error.
>
> I tried to git-revert just this one commit, but I get merge conflicts
> I don't how to resolve.
>
> BTW, I just discovered tons of kernel debugging config options which
> were turned off -- I just turned several of them on. Maybe I can give
> you better info now.
>
OK, this is the changeset I'd expect to cause problems. I'll try to
repo it here.
J
prev parent reply other threads:[~2006-12-11 1:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-11 0:07 2.6.19-rc6-mm2 hangs when gdb is run on a multithread program Pedro Larroy Tovar
2006-12-11 0:45 ` Jeremy Fitzhardinge
2006-12-11 1:30 ` walt
2006-12-11 1:45 ` Jeremy Fitzhardinge [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=457CB83C.5060107@goop.org \
--to=jeremy@goop.org \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=w41ter@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