Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Girish Shilamkar <girish@linsyssoft.com>
To: Daniel Jacobowitz <drow@false.org>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [Patch] Mark the thread_event breakpoint as "not inserted" 	before   calling thread_mourn_inferior
Date: Fri, 20 Jan 2006 14:14:00 -0000	[thread overview]
Message-ID: <1137766638.3225.40.camel@krypton> (raw)
In-Reply-To: <20060118135735.GA3154@nevyn.them.org>

> As I suspected something is wrong with your host system, kernel,
> environment, or similar.  You may want to try a few others.
	Thanks for the reply. I tried gdb-6.4 on Fedora Core 3 & 4 and always
saw that problem. I further tried gdb-6.3 on the same m/c with same
configuration (only the gdb had changed )on which I had seen this
problem and it worked fine. 
	Then while investigating further about the different behaviour of the
two gdb's i.e. gdb-6.3 and gdb-6.4 I found one difference that gdb-6.3
doesn't have a function called thread_db_xfer_partial.

	The following call trace is same for both the gdbs 

#11 0x08131c24 in target_write_memory (memaddr=4626416, myaddr=0x95a7618
"U",
            len=1) at ../../src/gdb/target.c:1013
#12 0x081305a2 in default_memory_remove_breakpoint (addr=4626416,
            contents_cache=0x95a7618 "U") at ../../src/gdb/mem-
break.c:78
#13 0x08124292 in gdbarch_memory_remove_breakpoint (gdbarch=0x9545f90,
            addr=4626416, contents_cache=0x95a7618 "U")
at ../../src/gdb/gdbarch.c:2960
#14 0x081305e0 in memory_remove_breakpoint (addr=4626416,
            contents_cache=0x95a7618 "U") at ../../src/gdb/mem-
break.c:91
#15 0x080cffdd in remove_breakpoint (b=0x95a7600, is=mark_inserted)
    at ../../src/gdb/breakpoint.c:1452
#16 0x080d82aa in delete_breakpoint (bpt=0x95a7558)
        at ../../src/gdb/breakpoint.c:6772
#17 0x080d4258 in remove_thread_event_breakpoints ()
            at ../../src/gdb/breakpoint.c:4295
#18 0x08096875 in thread_db_mourn_inferior ()
                at ../../src/gdb/linux-thread-db.c:1107
#19 0x0810da19 in handle_inferior_event (ecs=0xfefa4cb0)
                    at ../../src/gdb/infrun.c:1376
                    (More stack frames follow...)

	in target_write_memory, gdb-6.3 calls target_xfer_memory whereas
gdb-6.4 calls xfer_using_stratum this difference is there since
target_stack->to_xfer_partial is set to deafult_xfer_partial for gdb-6.3
whereas it is set to thread_db_xfer_partial for gdb-6.4
	So the further functions which are called for gdb-6.4 are
xfer_using_stratum -> target_xfer_partial -> thread_db_xfer_partial

And in thread_db_xfer_partial it checks whether the thread is alive or
not (target_thread_alive) and while doing so it tries to fetch registers
ptrace(PTRACE_GETREGS,.....) and fails.

	Kindly let me know what's wrong?

Thanks & Regards,
-Girish.
	




  reply	other threads:[~2006-01-20 14:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-17 15:35 Girish Shilamkar
2006-01-17 15:40 ` Daniel Jacobowitz
2006-01-18  9:11   ` Girish Shilamkar
2006-01-18 13:57     ` Daniel Jacobowitz
2006-01-20 14:14       ` Girish Shilamkar [this message]
2006-01-20 14:35         ` Daniel Jacobowitz
2006-01-23  9:21           ` Girish Shilamkar
2006-01-24 21:52             ` Daniel Jacobowitz

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=1137766638.3225.40.camel@krypton \
    --to=girish@linsyssoft.com \
    --cc=drow@false.org \
    --cc=gdb-patches@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