public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Manoj Iyer <manjo@austin.ibm.com>
To: Michael Chastain <mec.gnu@mindspring.com>
Cc: gdb@sources.redhat.com
Subject: thread testcase compile issue (question)
Date: Thu, 05 Aug 2004 23:26:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.58.0408051442240.29091@lazy> (raw)
In-Reply-To: <Pine.LNX.4.58.0408051004010.29091@lazy>


When I execute tests under gdb.threads/ directory for instance killed.exp,
I see 2 complies of the same testcase, the first one gets a linker error
/usr/bin/ld: cannot find -lpthreads but the second time it works with no
errors. Anyone has any idea why???

Here is the output on x86 for you to compare:

                === gdb tests ===

Schedule of variations:
    unix

Running target unix
Using /home/manjo/projects/gdb/june/src/dejagnu/baseboards/unix.exp as
board des
cription file for target.
Using /home/manjo/projects/gdb/june/src/dejagnu/config/unix.exp as generic
inter
face file for target.
Using ./config/unix.exp as tool-and-target-specific interface file.
Running ./gdb.threads/killed.exp ...
Executing on host: gcc ./gdb.threads/killed.c
-I/home/manjo/projects/gdb/june/s
rc/gdb/testsuite -g  -lpthreads -lm   -o
/home/manjo/projects/gdb/june/src/gdb/t
estsuite/gdb.threads/killed    (timeout = 300)
/usr/bin/ld: cannot find -lpthreads
collect2: ld returned 1 exit status
compiler exited with status 1
output is:
/usr/bin/ld: cannot find -lpthreads
collect2: ld returned 1 exit status

Executing on host: gcc ./gdb.threads/killed.c
-I/home/manjo/projects/gdb/june/s
rc/gdb/testsuite -g  -lpthread -lm   -o
/home/manjo/projects/gdb/june/src/gdb/te
stsuite/gdb.threads/killed    (timeout = 300)
PASS: gdb.threads/killed.exp: successfully compiled posix threads test
case
GNU gdb 2004-06-30-cvs


Thanks
----- ----
Manoj Iyer
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
+ Cognito ergo sum                                                          +
+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

On Thu, 5 Aug 2004, Manoj Iyer wrote:

>
> Michael,
>
> I tried ur suggestion but it still did not work, so I used send_gdb and
> gdb_expect{} and got it to work. Thanks for the help.
>
> Thanks
> ----- ----
> Manoj Iyer
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
> + Cognito ergo sum                                                          +
> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
> On Wed, 4 Aug 2004, Michael Chastain wrote:
>
> > I don't even use gdb_continue ... how about just plain:
> >
> >   gdb_test_multiple "continue" "continue to foo ..." {
> >     ...
> >   }
> >
> > Or maybe I'm not getting the problem.
> >
> > Michael C
> >
>

  reply	other threads:[~2004-08-05 23:26 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-04 20:45 testcase help Manoj Iyer
2004-08-04 22:44 ` Michael Chastain
2004-08-05 15:35   ` Manoj Iyer
2004-08-05 23:26     ` Manoj Iyer [this message]
2004-08-06  6:09       ` thread testcase compile issue (question) Michael Chastain

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=Pine.LNX.4.58.0408051442240.29091@lazy \
    --to=manjo@austin.ibm.com \
    --cc=gdb@sources.redhat.com \
    --cc=mec.gnu@mindspring.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).