From: Jon Masters <jonmasters@gmail.com>
To: Mark Powell <medp@primagraphics.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: gdb on a 440GP ELDK
Date: Thu, 21 Oct 2004 14:30:58 +0100 [thread overview]
Message-ID: <35fb2e5904102106303edb204b@mail.gmail.com> (raw)
In-Reply-To: <41777D14.7090108@primagraphics.com>
On Thu, 21 Oct 2004 10:10:44 +0100, Mark Powell <medp@primagraphics.com> wrote:
> The system seems to basically run fine apart from the fact that gdb
> doesn't stop at any breakpoints.
Can you please provide an example? How are you running the program
being debugged? If it's a daemon, are you running it interactively or
trying to let it detach itself?
Jon.
next prev parent reply other threads:[~2004-10-21 13:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-21 9:10 gdb on a 440GP ELDK Mark Powell
2004-10-21 13:30 ` Jon Masters [this message]
2004-10-21 14:43 ` Mark Powell
2004-10-22 9:40 ` Mark Powell
2004-10-22 17:20 ` Matt Porter
2004-10-21 17:52 ` Eugene Surovegin
2004-10-21 18:39 ` Matt Porter
2004-10-22 9:09 ` [PATCH][PPC32] IBM-EMAC fixes Gerhard Jaeger
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 21:20 gdb on a 440GP ELDK Glenn Burkhardt
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=35fb2e5904102106303edb204b@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=medp@primagraphics.com \
/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;
as well as URLs for NNTP newsgroup(s).