Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Michael Snyder <msnyder@vmware.com>
To: Amol Dixit <dixit@netapp.com>
Cc: "gdb@sourceware.org" <gdb@sourceware.org>
Subject: Re: breakpoint in gdbserver
Date: Sat, 30 Aug 2008 03:30:00 -0000	[thread overview]
Message-ID: <48B83583.4040007@vmware.com> (raw)
In-Reply-To: <48B835EC.4040509@netapp.com>

Amol Dixit wrote:
> 
> Michael Snyder wrote:
>> Dixit, Amol wrote:
>>> Hi,
>>> I am attempting to port gdbserver for freebsd (libpthread/libthr). While
>>> I may have complex doubts later, I will start with a simple one.
>>> I need to look at some gdbserver code path on Linux, and while I can set
>>> breakpoints and these functions are entered, gdb doesn't break at all.
>>> Gdbserver is compiled w/ symbols and I am using gdb6.8 to debug it.
>>> Any idea what I am missing here?
>>>
>>> (gdb) i b
>>> Num     Type           Disp Enb Address    What
>>> 1       breakpoint     keep y   0x0804f214 in main at ../server.c:1230
>>>         breakpoint already hit 1 time
>>> 2       breakpoint     keep y   0x0804d560 in start_inferior at
>>> ../server.c:91
>>> 3       breakpoint     keep y   0x0804b460 in add_thread at
>>> ../inferiors.c:101
>>>
>>> I can hit 1, but not 2 & 3 for example.
>> I assume you are using one gdb to debug gdbserver,
>> and a second gdb to talk to gdbserver's socket?
>>
> Correct.
> I can break in freebsd gdbserver build, but not linux (functions or line
> nos.).

How curious...


  reply	other threads:[~2008-08-29 17:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-30  0:15 Dixit, Amol
2008-08-30  0:44 ` Michael Snyder
2008-08-30  1:03   ` Amol Dixit
2008-08-30  3:30     ` Michael Snyder [this message]
2008-08-30 22:15 ` Ulrich Weigand

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=48B83583.4040007@vmware.com \
    --to=msnyder@vmware.com \
    --cc=dixit@netapp.com \
    --cc=gdb@sourceware.org \
    /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