Your message dated Sat, 09 Mar 2013 16:11:19 +0000 with message-id <1362845479.3768.495.ca...@deadeye.wl.decadent.org.uk> and subject line Re: Bug#691576: GDB stops with sigtrap at 0 address on ia64 wheezy has caused the Debian Bug report #691576, regarding GDB stops with sigtrap at 0 address on ia64 wheezy to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact ow...@bugs.debian.org immediately.) -- 691576: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=691576 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
--- Begin Message ---Package: gdb Version: 7.4.1 Severity: serious Dell PowerEdge 3250 2x Itanium Madison 1.5GHz 6M 4GB RAM I realized that GDB doesn't work as it should.When GDB should run *any* target application, it always stops with SIGTRAP 0x0000000000000000.Example: stephan@itanic:~$ gdb man GNU gdb (GDB) 7.4.1-debian Copyright (C) 2012 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 "ia64-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/man...(no debugging symbols found)...done. (gdb) run Starting program: /usr/bin/man Program received signal SIGTRAP, Trace/breakpoint trap. 0x0000000000000000 in ?? () (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. 0x0000000000000000 in ?? () (gdb) c Continuing. Program received signal SIGTRAP, Trace/breakpoint trap. 0x0000000000000000 in ?? () (gdb) Debian Wheezy: Kernel 3.2.23, GDB 7.4.1 doesn't work Debian Wheezy: Kernel 3.2.23, GDB 7.3 doesn't work Debian Wheezy: with Kernel 3.5.5 (experimental), GDB 7.4.1 doesn't work Debian Wheezy: with Kernel 3.5.5 (experimental), GDB 7.3 doesn't workDebian Lenny: Kernel 2.6.26, a 'debootstrapped' Wheezy userland, GDB 7.4.1 *works*Gentoo: Kernel 3.3.8, GDB 7.3.1 worksI'm surprised that GDB 7.4.1 works on Lenny in the chroot'd Wheezy environment.Please also note that the problem doesn't occur on Gentoo ia64. In my opinion, it points to the Debian Kernel somehow... Stephan
--- End Message ---
--- Begin Message ---On Sat, 2013-03-09 at 15:35 +0100, Stephan Schreiber wrote: > notfound 691576 src:linux/3.5.5-1~experimental.1 > notfixed 691576 linux-image-3.0.0-2-mckinley/3.0.0-5 > notfixed 691576 linux-image-3.1.0-rc7-mckinley/3.1.0~rc7-1~experimental.1 > fixed 691576 3.2.35-2 > thanks > > > The problem with GDB does no longer occur with Kernel 3.2.35-2. I > don't have a clue why. > A user has confimred that on the debian-i...@lists.debian.org list. > > I filed a new bug#702641 for the asm register contraints problem above. > > Please could you simply close this bug? Done. (But you can close bugs yourself, just as you can change their versions.) Ben. -- Ben Hutchings Always try to do things in chronological order; it's less confusing that way.signature.asc
Description: This is a digitally signed message part
--- End Message ---