* [Bug breakpoints/17768] GDB for ARM does not allow breakpoints on some addresses
2014-12-28 11:50 [Bug breakpoints/17768] New: GDB for ARM does not allow breakpoints on some addresses mark4th at gmail dot com
@ 2014-12-28 17:46 ` dje at google dot com
2014-12-28 22:44 ` mark4th at gmail dot com
` (3 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: dje at google dot com @ 2014-12-28 17:46 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=17768
dje at google dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dje at google dot com
--- Comment #1 from dje at google dot com ---
This is a pretty data-free bug report.
Got repro?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug breakpoints/17768] GDB for ARM does not allow breakpoints on some addresses
2014-12-28 11:50 [Bug breakpoints/17768] New: GDB for ARM does not allow breakpoints on some addresses mark4th at gmail dot com
2014-12-28 17:46 ` [Bug breakpoints/17768] " dje at google dot com
@ 2014-12-28 22:44 ` mark4th at gmail dot com
2014-12-29 5:04 ` dje at google dot com
` (2 subsequent siblings)
4 siblings, 0 replies; 6+ messages in thread
From: mark4th at gmail dot com @ 2014-12-28 22:44 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=17768
--- Comment #2 from Mark Manning <mark4th at gmail dot com> ---
what data would you like?
what is repro?
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug breakpoints/17768] GDB for ARM does not allow breakpoints on some addresses
2014-12-28 11:50 [Bug breakpoints/17768] New: GDB for ARM does not allow breakpoints on some addresses mark4th at gmail dot com
2014-12-28 17:46 ` [Bug breakpoints/17768] " dje at google dot com
2014-12-28 22:44 ` mark4th at gmail dot com
@ 2014-12-29 5:04 ` dje at google dot com
2014-12-29 9:04 ` mark4th at gmail dot com
2014-12-29 11:38 ` mark4th at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: dje at google dot com @ 2014-12-29 5:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=17768
--- Comment #3 from dje at google dot com ---
Sorry, "repro" == "reproduction".
How do I recreate the problem?
Be as explicit as possible, don't leave anything out.
e.g., what test program can I use?
Got a complete transcript of a gdb session that shows the problem?
etc. etc. etc.
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread
* [Bug breakpoints/17768] GDB for ARM does not allow breakpoints on some addresses
2014-12-28 11:50 [Bug breakpoints/17768] New: GDB for ARM does not allow breakpoints on some addresses mark4th at gmail dot com
` (2 preceding siblings ...)
2014-12-29 5:04 ` dje at google dot com
@ 2014-12-29 9:04 ` mark4th at gmail dot com
2014-12-29 11:38 ` mark4th at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: mark4th at gmail dot com @ 2014-12-29 9:04 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=17768
--- Comment #4 from Mark Manning <mark4th at gmail dot com> ---
actually now I cant reproduce it, my GDB must have been in an insane state
when I posted the bug, it would not allow me to set any breakpoint on any
address unless it was 32 bit aligned.... now it will !
On Mon, Dec 29, 2014 at 12:04 AM, dje at google dot com <
sourceware-bugzilla@sourceware.org> wrote:
> https://sourceware.org/bugzilla/show_bug.cgi?id=17768
>
> --- Comment #3 from dje at google dot com ---
> Sorry, "repro" == "reproduction".
>
> How do I recreate the problem?
> Be as explicit as possible, don't leave anything out.
> e.g., what test program can I use?
> Got a complete transcript of a gdb session that shows the problem?
> etc. etc. etc.
>
> --
> You are receiving this mail because:
> You reported the bug.
>
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread* [Bug breakpoints/17768] GDB for ARM does not allow breakpoints on some addresses
2014-12-28 11:50 [Bug breakpoints/17768] New: GDB for ARM does not allow breakpoints on some addresses mark4th at gmail dot com
` (3 preceding siblings ...)
2014-12-29 9:04 ` mark4th at gmail dot com
@ 2014-12-29 11:38 ` mark4th at gmail dot com
4 siblings, 0 replies; 6+ messages in thread
From: mark4th at gmail dot com @ 2014-12-29 11:38 UTC (permalink / raw)
To: gdb-prs
https://sourceware.org/bugzilla/show_bug.cgi?id=17768
--- Comment #5 from Mark Manning <mark4th at gmail dot com> ---
actually, there is still something wrong, i set a breakpoint on address
0xnnnn and the breakpoint gets inserted somewhere else close by but within
a few opcodes, not at the specified location. I can not supply you with
anything other than my executable and a description of how to reproduce the
problem.
This is with gdb v 7.8.1 running on my beagleboard xm under gentoo (arm
cortex-a7 processor but cortex-m4 code)
i woluld have no objections to sending you my sources if that helps
On Mon, Dec 29, 2014 at 4:03 AM, Mark Manning <mark4th@gmail.com> wrote:
> actually now I cant reproduce it, my GDB must have been in an insane state
> when I posted the bug, it would not allow me to set any breakpoint on any
> address unless it was 32 bit aligned.... now it will !
>
>
> On Mon, Dec 29, 2014 at 12:04 AM, dje at google dot com <
> sourceware-bugzilla@sourceware.org> wrote:
>
>> https://sourceware.org/bugzilla/show_bug.cgi?id=17768
>>
>> --- Comment #3 from dje at google dot com ---
>> Sorry, "repro" == "reproduction".
>>
>> How do I recreate the problem?
>> Be as explicit as possible, don't leave anything out.
>> e.g., what test program can I use?
>> Got a complete transcript of a gdb session that shows the problem?
>> etc. etc. etc.
>>
>> --
>> You are receiving this mail because:
>> You reported the bug.
>>
>
>
>
> --
> “When something can be read without effort,
> great effort has gone into its writing.”
>
> ― Enrique Jardiel Poncela ―
>
--
You are receiving this mail because:
You are on the CC list for the bug.
>From gdb-prs-return-17222-listarch-gdb-prs=sources.redhat.com@sourceware.org Mon Dec 29 13:16:53 2014
Return-Path: <gdb-prs-return-17222-listarch-gdb-prs=sources.redhat.com@sourceware.org>
Delivered-To: listarch-gdb-prs@sources.redhat.com
Received: (qmail 810 invoked by alias); 29 Dec 2014 13:16:52 -0000
Mailing-List: contact gdb-prs-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <gdb-prs.sourceware.org>
List-Subscribe: <mailto:gdb-prs-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/gdb-prs/>
List-Post: <mailto:gdb-prs@sourceware.org>
List-Help: <mailto:gdb-prs-help@sourceware.org>, <http://sourceware.org/lists.html#faqs>
Sender: gdb-prs-owner@sourceware.org
Delivered-To: mailing list gdb-prs@sourceware.org
Received: (qmail 785 invoked by uid 48); 29 Dec 2014 13:16:51 -0000
From: "unavowed at vexillium dot org" <sourceware-bugzilla@sourceware.org>
To: gdb-prs@sourceware.org
Subject: [Bug gdb/17771] New: Crash parsing symbol
Date: Mon, 29 Dec 2014 13:16:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gdb
X-Bugzilla-Component: gdb
X-Bugzilla-Version: 7.8
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: unavowed at vexillium dot org
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P2
X-Bugzilla-Assigned-To: unassigned at sourceware dot org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
bug_severity priority component assigned_to reporter
Message-ID: <bug-17771-4717@http.sourceware.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
X-Bugzilla-URL: http://sourceware.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2014-q4/txt/msg00465.txt.bz2
Content-length: 1491
https://sourceware.org/bugzilla/show_bug.cgi?id\x17771
Bug ID: 17771
Summary: Crash parsing symbol
Product: gdb
Version: 7.8
Status: NEW
Severity: normal
Priority: P2
Component: gdb
Assignee: unassigned at sourceware dot org
Reporter: unavowed at vexillium dot org
$ cat test.c
int test __asm__
("_Z16affine_transformIddLm2EE6VectorIDTmlcvT__EcvT0__EEXT1_EERK6MatrixIS1_XplT1_Li1EEXplT1_Li1EEERKS0_IS2_XT1_EE");
int
main (void)
{
return 0;
}
$ gcc -o test test.c
$ gdb ./test
GNU gdb (GDB) 7.8
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-unknown-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./test...Segmentation fault (core dumped)
Also affects GNU c++filt (GNU Binutils) 2.25
--
You are receiving this mail because:
You are on the CC list for the bug.
^ permalink raw reply [flat|nested] 6+ messages in thread