From: Momchil Velikov <velco@fadata.bg>
To: balteo@wanadoo.fr
Cc: gdb@sources.redhat.com
Subject: Re: Help with GDB
Date: Tue, 02 Jul 2002 03:15:00 -0000 [thread overview]
Message-ID: <87k7oefnc1.fsf@fadata.bg> (raw)
In-Reply-To: <3D2131B100024376@mel-rta9.wanadoo.fr> (added by postmaster@wanadoo.fr)
>>>>> "Balteo" == Balteo <balteo@wanadoo.fr> writes:
Balteo> Hello,
Balteo> I am compiling a C program from several source files and the "list" comma=
Balteo> nd=20
Balteo> of gdb always results in a "init.c: no such file or directory". Note that=
Balteo> the=20
Balteo> problem does not happen when the program is made on only one source file.
Balteo> How can I make gdb work with several source files?
GDB works fine with several source files. Don't forget to add a line
number after the colon, i.e.,
l <file>:<line>
Regards,
-velco
PS. Probably you'll consider changing your MUA, SpamAssassin
classifies your message as spam.
SPAM: -------------------- Start SpamAssassin results ----------------------
SPAM: This mail is probably spam. The original message has been altered
SPAM: so you can recognise or block similar unwanted mail in future.
SPAM: See http://spamassassin.org/tag/ for more details.
SPAM:
SPAM: Content analysis details: (9.1 hits, 5 required)
SPAM: FROM_NAME_NO_SPACES (-0.1 points) From: no spaces in name
SPAM: MSG_ID_ADDED_BY_MTA (4.0 points) 'Message-Id' was added by a relay
SPAM: INVALID_MSGID (1.8 points) Message-Id is not valid, according to RFC-2822
SPAM: DATE_IN_FUTURE_03_06 (3.4 points) Date: is 3 to 6 hours after Received: date
SPAM:
SPAM: -------------------- End of SpamAssassin results ---------------------
prev parent reply other threads:[~2002-07-02 10:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-02 2:28 Balteo
2002-07-02 3:15 ` Momchil Velikov [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=87k7oefnc1.fsf@fadata.bg \
--to=velco@fadata.bg \
--cc=balteo@wanadoo.fr \
--cc=gdb@sources.redhat.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