mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Andrew Morton <akpm@osdl.org>,
	kernel list <linux-kernel@vger.kernel.org>
Cc: marcel@holtmann.org, maxk@qualcomm.com,
	bluez-devel@lists.sourceforge.net
Subject: ptrace() memory corruption?
Date: Sun, 24 Dec 2006 01:07:54 +0100	[thread overview]
Message-ID: <20061224000753.GA1811@elf.ucw.cz> (raw)
In-Reply-To: <20061224000605.GA1768@elf.ucw.cz>

On Sun 2006-12-24 01:06:05, Pavel Machek wrote:
> On Sun 2006-12-24 01:01:50, Pavel Machek wrote:
> > Hi!
> > 
> > > > I got this nasty oops while playing with debugger. Not sure if that is
> > > > related; it also might be something with bluetooth; I already know it
> > > > corrupts memory during suspend, perhaps it corrupts memory in some
> > > > error path?
> > > 
> > > Okay, I spoke too soon. bluetooth & suspend memory corruption was
> > > _way_ harder to reproduce than expected. Took me 5-or-so-suspend
> > > cycles... so it is probably unrelated to the previous crash.
> > > 
> > > I was getting pretty regular crashes with bluetooth & gdb, but I was
> > > not using bluetooth at the time of ext3-related crash.
> > 
> > And for completeness, here's bluetooth + gdb oops. Ok, I'm not _sure_
> > it is bluetooth related. I'll try it without bluetooth in a while.
> 
> Ok, so this one is not bluetooth related. My little "phone"
> application provokes nasty oops, even when talking to
> /dev/null. Strange, that code does _nothing_
> strange. (www.sf.net/projects/tui).
> 
> Is there something wrong with gdb?

Yep. If I do gdb /bin/bash, run; I'll get similar oops. Am I alone
seeing this?
									Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2006-12-24  0:08 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-23 23:43 ext3-related crash in 2.6.20-rc1 Pavel Machek
2006-12-23 23:55 ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Pavel Machek
2006-12-24  0:01   ` Pavel Machek
2006-12-24  0:06     ` not-only-bluetooth memory corruption Pavel Machek
2006-12-24  0:07       ` Pavel Machek [this message]
2006-12-24  1:14         ` ptrace() memory corruption? Jiri Slaby
2006-12-24 11:52           ` Jiri Slaby
2006-12-24 12:22             ` Andrew Morton
2006-12-24 13:44               ` Jiri Slaby
2006-12-24  1:18   ` bluetooth memory corruption (was Re: ext3-related crash in 2.6.20-rc1) Andrew Morton
2006-12-24 23:24     ` Pavel Machek
2006-12-24 14:39   ` Marcel Holtmann
2006-12-24 23:36     ` Pavel Machek
2006-12-30 21:52       ` Adrian Bunk
2007-01-01 19:01         ` Pavel Machek
2006-12-24 23:43     ` Pavel Machek
2006-12-28  8:42       ` Pavel Machek
2006-12-28 10:40         ` Marcel Holtmann
2006-12-24  1:12 ` ext3-related crash in 2.6.20-rc1 Andrew Morton

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=20061224000753.GA1811@elf.ucw.cz \
    --to=pavel@ucw.cz \
    --cc=akpm@osdl.org \
    --cc=bluez-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=maxk@qualcomm.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

Powered by JetHome