From: Jim Blandy <jimb@red-bean.com>
To: Paul Hughes <paulh@ot.com.au>
Cc: gdb@sourceware.org
Subject: Re: gdb won't stop at break point in simple program
Date: Fri, 10 Feb 2006 07:13:00 -0000 [thread overview]
Message-ID: <8f2776cb0602092313h4d48cef4o2c334e71b4736d40@mail.gmail.com> (raw)
In-Reply-To: <43EC22CF.5070402@ot.com.au>
On 2/9/06, Paul Hughes <paulh@ot.com.au> wrote:
> I've just written the simplest program I could.
> I set a break point in main and run the program.
> Gdb prints out some odd messages
> "Detaching after fork from child process XXXXX"
> Program ends without stopping at the break point.
> Can anyone shed any light on what is going on here?
Wow. You're using the GDB and GCC included with your distribution?
I know the current GDB sources don't behave this way; the GDB test
suite does the equivalent of your test, and more, many, many times, so
there's no way we could have missed it.
I think there's something very strange going on on your machine.
next prev parent reply other threads:[~2006-02-10 7:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-10 5:22 Paul Hughes
2006-02-10 7:13 ` Jim Blandy [this message]
2006-02-11 0:54 ` Paul Hughes
2006-02-11 5:27 ` Jim Blandy
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=8f2776cb0602092313h4d48cef4o2c334e71b4736d40@mail.gmail.com \
--to=jimb@red-bean.com \
--cc=gdb@sourceware.org \
--cc=paulh@ot.com.au \
/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