From: ekara@uekae.tubitak.gov.tr
To: ekara@uekae.tubitak.gov.tr
Cc: pgilliam@us.ibm.com, gdb-patches@sources.redhat.com
Subject: Re:[patch] "single step" atomic instruction sequences as a whole.
Date: Wed, 13 Sep 2006 11:14:00 -0000 [thread overview]
Message-ID: <20060913110820.6C27D490164@uekae.uekae.gov.tr> (raw)
In-Reply-To: <20060913110230.8EABD490164@uekae.uekae.gov.tr>
Sorry forgot the logs.
--------------------test function.
#include <stdio.h>
#define __KERNEL__
#include <asm/atomic.h>
atomic_t i;
int main(void)
{
printf("atomic_step_test\n");
atomic_set(&i,5);
printf("i=%d\n",atomic_read(&i));
atomic_dec(&i);
printf("i=%d\n",atomic_read(&i));
}
----------- gdb logs-----------
Breakpoint 2, main () at test.c:8
8 printf("atomic_step_test\n");
(gdb) next
9 atomic_set(&i,5);
(gdb) next
10 printf("i=%d\n",atomic_read(&i));
(gdb) next
151 :"=m" (v->counter), "=qm" (c)
(gdb) next
Stepping over an atomic sequence of instructions beginning at 0x10000484
breakpoint.c:7730: internal-error: remove_single_step_breakpoints:
Assertion `single_step_breakpoints[0] != NULL' failed.
A problem internal to GDB has been detected,
further debugging may prove unreliable.
Quit this debugging session? (y or n)
--------------------------
Regards.
Emre
> Hello Mr Gilliam;
> Firstly thank you very much for your patch about single stepping problem
> on atomic instructions. In my opinion, this bug is very critical for
> powerpc arch (especially while kernel debugging). We have experienced this
> problem with both with h/w probe (BDI2000) and KGDB while debugging
> kernel. I have applied your patch to latest gdb (20060911 taken from cvs)
> and after correctting some fail warnings and test it on a PPC8540. It can
> successfullt detects 'lwarx' instruction but can't step over the loop and
> a little moment later, it gives an error message like 'breakpoint.c:7730:
> internal-error: remove_single_step_breakpoints: Assertion
> `single_step_breakpoints[0] != NULL' failed.'
> I have corrected some patch error, I dont know, maybe this is the reason
> of the problem. Here is the output of gdb and my test program that include
> atomic_dec function.
> Where can be the problem? And thank alot again, because atomic functions
> are everywhere on kernel waiting to cause infinite loops..
> Regards.
> Emre KARA
>
>
>
next parent reply other threads:[~2006-09-13 11:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20060913110230.8EABD490164@uekae.uekae.gov.tr>
2006-09-13 11:14 ` ekara [this message]
2006-09-18 11:59 emin ak
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=20060913110820.6C27D490164@uekae.uekae.gov.tr \
--to=ekara@uekae.tubitak.gov.tr \
--cc=gdb-patches@sources.redhat.com \
--cc=pgilliam@us.ibm.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