From: "Bloch, Jack" <Jack.Bloch@icn.siemens.com>
To: "'gdb@sources.redhat.com'" <gdb@sources.redhat.com>
Subject: RE: What is gdb.base/structs2.exp actually testing?
Date: Mon, 08 Mar 2004 15:11:00 -0000 [thread overview]
Message-ID: <7A25937D23A1E64C8E93CB4A50509C2A0310F0E8@stca204a.bus.sc.rolm.com> (raw)
I am trying to set a breakpoint in a shared library used by my executable. I
have the following two problesm. I try to set the path to the directory
where the source of my shared library is via the directory command. I do not
get an error back, but when I try to open this source file I get a file not
found (the file exists) error. Secondly, I saw some documentation about set
breakpoint pending on. I am not able to do this from my version of GDB. I am
running 5.2.1 on a SuSE 2.4.19 kernel.
What am I doing wrong?
Jack Bloch
Siemens ICN
phone (561) 923-6550
e-mail jack.bloch@icn.siemens.com
next reply other threads:[~2004-03-08 15:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-08 15:11 Bloch, Jack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-03-08 16:32 Michael Elizabeth Chastain
2004-03-08 14:42 Corinna Vinschen
2004-03-08 14:54 ` Daniel Jacobowitz
2004-03-08 15:07 ` Corinna Vinschen
2004-03-08 16:20 ` Andrew Cagney
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=7A25937D23A1E64C8E93CB4A50509C2A0310F0E8@stca204a.bus.sc.rolm.com \
--to=jack.bloch@icn.siemens.com \
--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