From: Markus Brandner <brandner@emt.tugraz.at>
To: gdb@sources.redhat.com
Subject: gdb refuses to 'break'
Date: Wed, 16 Apr 2003 18:18:00 -0000 [thread overview]
Message-ID: <200304162017.38789.brandner@emt.tugraz.at> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi!
Either I missed the point when reading the gdb documentation or
I'm just experiencing some strange behaviour in gdb.
Im running a Slackware 8.1 system on kernel 2.4.18 with
libc-2.2.5
When I compile the following code:
test.c:
#include <stdio.h>
int main(int argc, char **argv)
{
printf("Breakpoint test\n");
return 0;
}
using "gcc -g test.c -o test" (my gcc is 2.95.3)
and try to set a break-point with gdb 5.2:
(gdb) break main
Breakpoint 1 at 0x80483f6: file test.c, line 5.
(gdb) run
Starting program: /home/home_PCs105/brandner/tmp/test
Breakpoint test
Program exited normally.
You can't do that without a process to debug.
(gdb)
gdb seems to run straight through ignoring the break.
I tried break: line number - same result
I even get the same results using gdb 5.3.
However, compiling the same source using the same gcc
on a libc-2.2.3 machine (kernel 2.2.21) and trying to
do the same thing using gdb 5.0 works perfectly
(but not with any more recent gdb version)
What am I missing?
Thanks for your help,
Markus
- --
- -----------------------------------------------------------------
Markus Brandner Institute of Electrical Measurement
and Measurement Signal Processing
phone: +43 316 873 7773 Graz University of Technology
fax: +43 316 873 4279 Schiessstattgasse 14B
email: brandner@emt.tugraz.at A8010 Graz, Austria
- -----------------------------------------------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE+nZ5BjjwO/+h9egkRAtf5AKCPC8DmjWw4L4ktKIMppsMvH+PSmQCglfUw
otygkEI0FAtE7vh6FVvLr4o=
=2tWf
-----END PGP SIGNATURE-----
next reply other threads:[~2003-04-16 18:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-16 18:18 Markus Brandner [this message]
2003-04-16 19:51 ` return type of a fucntion Smita
2003-04-16 19:59 ` gdb's communication to a process/libgdb? Smita
2003-04-16 20:04 ` Daniel Jacobowitz
2003-04-16 22:07 ` libgdb Smita
2003-04-16 23:58 ` is libgdb okay to use? Smita
2003-04-17 1:44 ` libgdb Elena Zannoni
2003-04-17 2:06 ` libgdb Smita
2003-04-17 2:12 ` finish implementation Smita
2003-04-17 12:57 ` libgdb Elena Zannoni
2003-04-17 2:11 ` finish for nested function calls Smita
2003-04-17 3:37 ` return type of a fucntion Peter Barada
2003-04-17 9:13 ` gdb refuses to 'break' Markus Brandner
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=200304162017.38789.brandner@emt.tugraz.at \
--to=brandner@emt.tugraz.at \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).