From: Brian Foster <brian.foster@innova-card.com>
To: jfraser@broadcom.com
Cc: linux-mips@linux-mips.org,
"Maciej W. Rozycki" <macro@linux-mips.org>,
TriKri <kristoferkrus@hotmail.com>
Subject: Re: Debugging the MIPS processor using GDB
Date: Wed, 13 Aug 2008 17:12:34 +0200 [thread overview]
Message-ID: <200808131712.34722.brian.foster@innova-card.com> (raw)
In-Reply-To: <1218638494.21039.6.camel@chaos.ne.broadcom.com>
On Wednesday 13 August 2008 16:41:34 Jon Fraser wrote:
> I use the FS2 probe with sde-gdb on a nearly daily basis.
> Are you compiling your kernel with -g -O1 ?
Jon,
‘-g’, yes. ‘-O1’? Not sure, I will have to check when
I get a chance. (But I don't see how either would have
the effect on breakpoints I'm suffering from?)
> You can also try 'hbreak' instead of 'break' in sde-gdb.
I'll have to (re-)try that when I get a chance. I did
try it once, and have (very! vague!!) memories of some
issue, but now cannot recall anything useful. ;-\
cheers!
-blf-
--
“How many surrealists does it take to | Brian Foster
change a lightbulb? Three. One calms | somewhere in south of France
the warthog, and two fill the bathtub | Stop E$$o (ExxonMobil)!
with brightly-coloured machine tools.” | http://www.stopesso.com
prev parent reply other threads:[~2008-08-13 15:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-12 13:23 Debugging the MIPS processor using GDB TriKri
2008-08-12 14:14 ` Martin Gebert
2008-08-12 14:37 ` Brian Foster
2008-08-12 16:27 ` Maciej W. Rozycki
2008-08-13 7:05 ` Brian Foster
2008-08-13 13:49 ` Maciej W. Rozycki
2008-08-13 15:07 ` Brian Foster
2008-08-13 15:16 ` Maciej W. Rozycki
2008-08-14 11:42 ` Debugging the MIPS processor using GDB (and FS2 EJTAG probe breakpoint issues) Brian Foster
2008-08-14 23:11 ` Maciej W. Rozycki
2008-08-13 14:41 ` Debugging the MIPS processor using GDB Jon Fraser
2008-08-13 15:12 ` Brian Foster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200808131712.34722.brian.foster@innova-card.com \
--to=brian.foster@innova-card.com \
--cc=jfraser@broadcom.com \
--cc=kristoferkrus@hotmail.com \
--cc=linux-mips@linux-mips.org \
--cc=macro@linux-mips.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox