public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Andreas Westin <andwes-8@student.luth.se>
To: Andrew Cagney <ac131313@redhat.com>
Cc: gdb@sources.redhat.com
Subject: Re: thread debugging problem
Date: Mon, 15 Sep 2003 13:10:00 -0000	[thread overview]
Message-ID: <1063631405.3f65ba2d032c4@webmail.student.luth.se> (raw)
In-Reply-To: <3F64FE2B.8070209@redhat.com>

> But GDB isn't loading it :-(  If it was (with a current [native] GDB) 
> you would see a message indicating it had been loaded.
> 
> Suggest checking that your gdb includes thread-db.o:thread_db_load, set
> 
> a breakpoint on that and see what happens.

I've switched to redhat9 and now I get thread info, but I'm having other
problems instead. Strange behaviour which I believe shouldn't happen.
When I step forward in the code it seems to be running into somekind of loop
running the same lines of code several times when it shouldn't, as you can see
in the gdb session below. This is with gdb 5.3.91 but I saw the same behaviour
with 5.3 on my gentoo box at home.

Any thoughts ?

Breakpoint 3, monitor_thread_main (arg=0x0) at monitor.c:481
481         if(prio->first)
(gdb) print prio->first
$10 = (struct listitem_t *) 0x805a7f8
(gdb) print prio->first->data
$11 = (void *) 0x8059be8
(gdb) n
480                     next_probe.tv_sec += cfg_getint(cfg, "probe-interval");
(gdb)
481         if(prio->first)
(gdb)
480                     next_probe.tv_sec += cfg_getint(cfg, "probe-interval");
(gdb)
481         if(prio->first)
(gdb) list 480
475                      * the time for the next probe session, otherwise wait a
                                                                           nd go
476                      * on with the next probe session.
477                      */
478
479                     gettimeofday(&next_probe, 0);
480                     next_probe.tv_sec += cfg_getint(cfg, "probe-interval");
481         if(prio->first)
482           logmsg(LOG_ERR, "Ja: %d", timercmp(&((userdata_t*)prio->first->dat
                                                                          
a)->tv, &next_probe, <=));
483                     while(prio->first && timercmp(&((userdata_t*)prio->first
                                                                          
->data)->tv, &next_probe, <=))
484                     {
(gdb)


/Andreas

  reply	other threads:[~2003-09-15 13:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-11 17:09 Andreas Westin
2003-09-11 17:13 ` Elena Zannoni
2003-09-12  7:18   ` Andreas Westin
2003-09-12 14:30     ` Daniel Jacobowitz
2003-09-12 14:49       ` Andreas Westin
2003-09-14 23:48         ` Andrew Cagney
2003-09-15 13:10           ` Andreas Westin [this message]
2003-09-15 14:36 Michael Elizabeth 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=1063631405.3f65ba2d032c4@webmail.student.luth.se \
    --to=andwes-8@student.luth.se \
    --cc=ac131313@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).