Bug#734320: gdb-avr: Wrong memory map due to missing XML support

2014-01-15 Thread Hakan Ardo
Hi,
thanx for the report. I've upgraded to gdb 7.6 and enbaled xml
support. If you still believe it is misbehaving please open a new bug.
Also, please consider to make your case upstream:

http://www.gnu.org/software/gdb/bugs/

On Sun, Jan 5, 2014 at 11:05 PM, Johannes Deutsch
 wrote:
> Package: gdb-avr
> Version: 7.4-1+b1
> Severity: normal
>
> Dear Maintainer,
>
> the description of the following case is related to the debugging of a real 
> mcu
> with avr-gdb over avarice.
>
> If i want to set a breakpoint at a specific address in program space with the
> corresponding gdb command
>
> (gdb) break *0xfff
>
> gdb answers my approach with
>
> warning: Can not parse XML memory map; XML support was disabled at compile
> time
> Breakpoint 1 at 0x800dbe
>
> Although after continuing the execution gdb breaks at the right address, it
> looks like gdb creates a breakpoint in data space at first sight. In addition
> the warning is scary :)
>
> Instead of the message above one would expect a mere
>
> Breakpoint 1 at 0xdbe
>
> Best regards
>
>
>
> -- System Information:
> Debian Release: jessie/sid
>   APT prefers testing
>   APT policy: (500, 'testing')
> Architecture: i386 (i686)
>
> Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores)
> Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
>
> Versions of packages gdb-avr depends on:
> ii  libc62.17-97
> ii  libncurses5  5.9+20130608-1
> ii  libtinfo55.9+20130608-1
>
> gdb-avr recommends no packages.
>
> Versions of packages gdb-avr suggests:
> pn  gdb-doc  
>
> -- no debconf information



-- 
Håkan Ardö


--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org



Bug#734320: gdb-avr: Wrong memory map due to missing XML support

2014-01-05 Thread Johannes Deutsch
Package: gdb-avr
Version: 7.4-1+b1
Severity: normal

Dear Maintainer,

the description of the following case is related to the debugging of a real mcu
with avr-gdb over avarice.

If i want to set a breakpoint at a specific address in program space with the
corresponding gdb command

(gdb) break *0xfff

gdb answers my approach with

warning: Can not parse XML memory map; XML support was disabled at compile
time
Breakpoint 1 at 0x800dbe

Although after continuing the execution gdb breaks at the right address, it
looks like gdb creates a breakpoint in data space at first sight. In addition
the warning is scary :)

Instead of the message above one would expect a mere

Breakpoint 1 at 0xdbe

Best regards



-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (500, 'testing')
Architecture: i386 (i686)

Kernel: Linux 3.10-3-686-pae (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages gdb-avr depends on:
ii  libc62.17-97
ii  libncurses5  5.9+20130608-1
ii  libtinfo55.9+20130608-1

gdb-avr recommends no packages.

Versions of packages gdb-avr suggests:
pn  gdb-doc  

-- no debconf information


-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org