From: Michael Richardson <mcr@sandelman.ottawa.on.ca>
To: linuxppc-embedded@ozlabs.org
Subject: Re: stepping through atomic_dec_return
Date: Fri, 07 Oct 2005 13:46:42 -0400 [thread overview]
Message-ID: <21062.1128707202@marajade.sandelman.ottawa.on.ca> (raw)
In-Reply-To: Message from "Michael Richardson" <mcr@sandelman.ottawa.on.ca> of "Fri, 07 Oct 2005 13:15:28 EDT." <19942.1128705328@marajade.sandelman.ottawa.on.ca>
-----BEGIN PGP SIGNED MESSAGE-----
>>>>> "Michael" == Michael Richardson <mcr@sandelman.ottawa.on.ca> writes:
Michael> I can see how setting through this code with the debugger
Michael> could cause a problem, since there would be debug
Michael> exceptions, and there would be other code in the debug
Michael> stubs that could set the RESERVED=0. It's hard to know,
Michael> but it seems unlikely to me.
Actually, I'm wrong.
I was trying to single step through the code, since much of the code
is inline, and doing "n" in the debugger won't set a break point after
that statement, it may well single step through.
Setting a break point after the down() worked.
- --
] ON HUMILITY: to err is human. To moo, bovine. | firewalls [
] Michael Richardson, Xelerance Corporation, Ottawa, ON |net architect[
] mcr@xelerance.com http://www.sandelman.ottawa.on.ca/mcr/ |device driver[
] panic("Just another Debian GNU/Linux using, kernel hacking, security guy"); [
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Finger me for keys
iQCVAwUBQ0a0f4qHRg3pndX9AQHs7AP+NVMj0Wy3aT9j1XW6t2hZqgjzVZZpAFuV
8b6hPtMVh/SYv6KbdWD4EmxQ7WMqB1rmx6oknxo6l7zTKHFwqmeW3Nod7X/xhNjy
SW4H8U/y7RjuI68i0rf1jkpUff6+3prKRvnVQ6dml7xH6IygBqDHjVP2hZlut++3
l30N1y5x1mU=
=d/sP
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2005-10-07 17:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-07 17:15 stepping through atomic_dec_return Michael Richardson
2005-10-07 17:46 ` Michael Richardson [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=21062.1128707202@marajade.sandelman.ottawa.on.ca \
--to=mcr@sandelman.ottawa.on.ca \
--cc=linuxppc-embedded@ozlabs.org \
/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