- To: "Jonathan Larmour" <jlarmour at redhat dot co dot uk>
- Subject: RE: Breakpoints
- From: "Anthony Massa" <amassa at cts dot com>
- Date: Sun, 25 Jun 2000 17:28:09 -0700
- Reply-To: <amassa at cts dot com>
What I found is that the reason the debugger wasn't hitting the break points
is that in quicc_smc1.c on line 318 when the communications processor module
was being reset, the code wouldn't return from this call. I can't figure
out why this would happen only occasionally?
Any thoughts on this?
-----Original Message-----
From: jlarmour@cygnus.co.uk [mailto:jlarmour@cygnus.co.uk]On Behalf Of
Jonathan Larmour
Sent: Sunday, June 25, 2000 2:27 PM
To: amassa@cts.com
Cc: eCos
Subject: Re: Breakpoints
Anthony Massa wrote:
>
> Lately when I download a file using Insight (by selecting the RUN icon)
the
> program will download and not stop at my break points. I use File->Open
to
> bring up the image and source files. I then set the break point in
> cyg_user_start. I hit the RUN icon to download the image and then it runs
> without stopping at my break point. Do you know what could cause this
> behavior?
Sometimes there can be multiple cyg_user_start's floating around, and GDB
chooses the wrong one (it's a known problem), so be sure to set a
breakpoint on the cyg_user_start that actually gets executed.
Also try it on unoptimized code. Debugging optimized code can sometimes
(although fortunately rarely) fail.
Jifl
--
Red Hat, 35 Cambridge Place, Cambridge, UK. CB2 1NS Tel: +44 (1223) 728762
"Plan to be spontaneous tomorrow." || These opinions are all my own fault