public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug ada/41419] New: [450 regression] many new ACATs failures (breakpoint instruction in object)
Date: Sun, 20 Sep 2009 15:15:00 -0000 [thread overview]
Message-ID: <bug-41419-296@http.gcc.gnu.org/bugzilla/> (raw)
Starting program:
/users/joel/test-gcc/gcc-svn/gcc/testsuite/ada/acats/work-jmr3904/tests/a/a85013b/a85013b
,.,. A85013B ACATS 2.5 88-01-01 00:00:00
---- A85013B CHECK THAT A SUBPROGRAM CAN BE RENAMED WITHIN ITS OWN BODY
AND THAT THE NEW NAME CAN BE USED IN A RENAMING
DECLARATION.
Program received signal SIGTRAP, Trace/breakpoint trap.
0x88004be8 in system.task_primitives.operations.create_task (t=0x881a2e90,
wrapper=(system.address) 0x8800c7c8, stack_size=<value optimized out>,
priority=122) at s-taprop.adb:962
962 Adjusted_Stack_Size - Adjusted_Stack_Size mod Page_Size;
Current language: auto
The current source language is "auto; currently ada".
(gdb) bt
#0 0x88004be8 in system.task_primitives.operations.create_task (t=0x881a2e90,
wrapper=(system.address) 0x8800c7c8, stack_size=<value optimized out>,
priority=122) at s-taprop.adb:962
#1 0x8800bbe0 in system.tasking.stages.activate_tasks (
chain_access=<value optimized out>) at s-tassta.adb:291
#2 0x8800390c in _ada_a85013b ()
(gdb)
When I disassemble at 0x88004be8, I see this:
0x88004be0 <system__task_primitives__operations__create_task+136>: bnez
s4,0x88004bec <system__task_primitives__operations__create_task+148>
0x88004be4 <system__task_primitives__operations__create_task+140>: divu
zero,s5,s4
0x88004be8 <system__task_primitives__operations__create_task+144>: break
0x7
To confirm this was actually in the program executable, I objdump'ed it.
88004be0: 16800002 bnez s4,88004bec
<system__task_primitives__operations__create_task+0x94>
88004be4: 02b4001b divu zero,s5,s4
88004be8: 0007000d break 0x7
--
Summary: [450 regression] many new ACATs failures (breakpoint
instruction in object)
Product: gcc
Version: 4.5.0
Status: UNCONFIRMED
Severity: normal
Priority: P3
Component: ada
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: joel at gcc dot gnu dot org
GCC target triplet: mips-rtems4.10
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41419
next reply other threads:[~2009-09-20 15:15 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-20 15:15 joel at gcc dot gnu dot org [this message]
2009-09-20 15:21 ` [Bug ada/41419] " joel at gcc dot gnu dot org
2009-09-20 15:33 ` laurent at guerby dot net
2009-09-20 15:56 ` joel at gcc dot gnu dot org
2009-09-20 16:28 ` laurent at guerby dot net
2009-09-20 16:40 ` joel at gcc dot gnu dot org
2009-09-20 16:46 ` joel at gcc dot gnu dot org
2009-09-20 16:58 ` charlet at gcc dot gnu dot org
2009-09-20 16:59 ` laurent at guerby dot net
2009-09-20 17:12 ` joel at gcc dot gnu dot org
2009-09-20 19:40 ` joel at gcc dot gnu dot org
2009-09-20 21:00 ` [Bug ada/41419] [4.5 " pinskia at gcc dot gnu dot org
2009-09-22 13:07 ` joel at gcc dot gnu dot org
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=bug-41419-296@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).