From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonathan Larmour To: "Boris V. Guzhov" Cc: ecos-discuss@sourceware.cygnus.com Subject: Re: [ECOS] gdb 'next' problem with i386 HAL Date: Fri, 17 Aug 2001 06:17:00 -0000 Message-id: <3B7D198D.89110FA1@redhat.com> References: <01C125FD.4894A7E0@bream.tr.localnet> <3B7BCE3A.92FDCA04@redhat.com> <000901c126ed$1c29f160$7601a8c0@int.spb.ru> X-SW-Source: 2001-08/msg00602.html "Boris V. Guzhov" wrote: > > Hi, > I also have such behaviour of the debugger. > My host Linux Redhat 6.2. > gdb version: i386-elf-gdb --verison returns GDB 5.0. > eCos version (with Redboot) from anon CVS (Juli 25) Okay, I don't know why that shouldn't work - certainly I was debugging on the PC target from the anon cvs code just last week. Perhaps it might behave better if the debugged app was built with no optimization. Other than that, you'll need to investigate further (e.g. by using "set debug remote 1" and seeing where GDB sets its "next" breakpoint and see if that's valid). Jifl -- Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062 Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine