By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
431,745 Members | 1,897 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 431,745 IT Pros & Developers. It's quick & easy.

debugging by gdb

P: n/a
Hi all,

I am using 'gdb' to debug my C++ program and it gives me the following
sentences:

Detaching after fork from child process 31404.
Detaching after fork from child process 31405.
Detaching after fork from child process 31406.
Detaching after fork from child process 31407.

any ideas about this problem?

Thanks,
Mohsen

Sep 21 '06 #1
Share this Question
Share on Google+
2 Replies


P: n/a
On 20 Sep 2006 17:48:34 -0700, "Mohsen" <ja*******@gmail.comwrote in
comp.lang.c++:
Hi all,

I am using 'gdb' to debug my C++ program and it gives me the following
sentences:

Detaching after fork from child process 31404.
Detaching after fork from child process 31405.
Detaching after fork from child process 31406.
Detaching after fork from child process 31407.

any ideas about this problem?

Thanks,
Mohsen
Yes, you are asking in the wrong place. This group is for the C++
language, which does not define the operations of specific compilers
or other tools, like linkers, librarians, profilers, and debuggers.

If this is on Linux, try asking in
news:comp.os.linux.development.apps. If not, try asking in one of the
gnu.* groups or mailing lists.

--
Jack Klein
Home: http://JK-Technology.Com
FAQs for
comp.lang.c http://c-faq.com/
comp.lang.c++ http://www.parashift.com/c++-faq-lite/
alt.comp.lang.learn.c-c++
http://www.contrib.andrew.cmu.edu/~a...FAQ-acllc.html
Sep 21 '06 #2

P: n/a
S S

Mohsen wrote:
Hi all,

I am using 'gdb' to debug my C++ program and it gives me the following
sentences:

Detaching after fork from child process 31404.
Detaching after fork from child process 31405.
Detaching after fork from child process 31406.
Detaching after fork from child process 31407.
This is not a problem, just when you attach some process to debugger,
other processes are also invoked depending on your program and it just
shows you message, safe to ignore.
any ideas about this problem?

Thanks,
Mohsen
Sep 21 '06 #3

This discussion thread is closed

Replies have been disabled for this discussion.