Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Vladimir Vorobyov <vladimir.vorobyov@iss.org.ua>
To: Daniel Jacobowitz <drow@false.org>, Andreas Schwab <schwab@suse.de>
Cc: gdb@sources.redhat.com
Subject: Re: pthreads debug with gdbserver
Date: Mon, 22 Nov 2004 14:07:00 -0000	[thread overview]
Message-ID: <200411221440.21131.vladimir.vorobyov@iss.org.ua> (raw)
In-Reply-To: <20041120013220.GB27485@nevyn.them.org>

> > As I said in my first message the breakpoint is hit exactly 3 times. I
found
> > that current_sos in solib-svr4.c can not find any libraries. It was
because
> > first_link_map_member returned NULL. After this I found that
> > SVR4_FETCH_LINK_MAP_OFFSETS did not return correct offsets (which are
correct
> > for me? ilp32?). I tried to follow those gdbach_data calls but it was
too
> > difficult. I just assigned svr4_ilp32_fetch_link_map_offsets to
> > SVR4_FETCH_LINK_MAP_OFFSETS (how to do it correctly?).
> > After this with every shlib breakpoint hit gdb loads appropriate shared
lib
> > BUT gdbserver reports "Target does not support breakpoints" 3 times for
each
> > library loaded. What does it mean ?
> > I still receive SIG32, info threads still shows only one thread. "info
shared"
> > shows all libraries that are loaded and td_ta_new() call now returns
> > successfully.
>
> Take a look at the source code to gdbserver.  Andreas, now I remember
> why I enabled thread_db support on a per-target basis - there are other
> support routines that have to be written.

> Yes, I have noticed that, too.  I'm currently trying to get it working for
> m68k (plus support for PTRACE_GETREGS).


> What routines should I add?

> Also I've added set_solib_svr4_fetch_link_map_offsets (gdbarch,
> svr4_ilp32_fetch_link_map_offsets) to m68klinux-tdep.c.
> It fixed the problem with bad link_map_offsets.

I think I've added all missing routines and it ALMOST work.
First, I have to specify 'set remotetimeout 60' otherwise gdb reports timeout 
error (Ignoring packet error, continuing...).
- Is it normal ?
Second, after I set any break point (e.g. break main) I cant use 'continue' 
command. Program stops after any instruction with SIGTRAP. When I force 
gdbserver to ignore 'stepping' variable, everything works fine. But Im sure 
it is wrong correction. Who is responsible for reseting stepping? And why we 
need it?

Thanks in advance.

Regards,
Vladimir.


  parent reply	other threads:[~2004-11-22 12:41 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-19 14:23 Vladimir Vorobyov
2004-11-19 14:42 ` Daniel Jacobowitz
2004-11-19 15:59   ` Vladimir Vorobyov
2004-11-20 10:01     ` Daniel Jacobowitz
2004-11-20 16:42       ` Vladimir Vorobyov
2004-11-20 16:57         ` Daniel Jacobowitz
2004-11-20 17:13           ` Andreas Schwab
2004-11-20 17:38           ` Vladimir Vorobyov
2004-12-06 18:41           ` NPTL on ppc (was: pthreads debug with gdbserver) Linh Dang
2004-12-06 18:45             ` Daniel Jacobowitz
2004-12-06 19:56               ` NPTL on ppc Linh Dang
2004-12-06 20:18                 ` Daniel Jacobowitz
2004-12-06 22:41                   ` Andreas Schwab
2004-12-06 23:20                   ` Andreas Schwab
2004-12-07 14:33                     ` Linh Dang
2004-12-07 14:56                       ` Andreas Schwab
2004-12-06 22:04                 ` Andreas Schwab
2004-11-22 14:07       ` Vladimir Vorobyov [this message]
2004-11-22 18:04         ` pthreads debug with gdbserver Daniel Jacobowitz
2004-11-23 19:33           ` Vladimir Vorobyov
2004-11-19 16:19 ` Andreas Schwab
2004-11-19 17:30   ` Vladimir Vorobyov
2004-11-20  1:31     ` Andreas Schwab
2004-11-20  1:32       ` 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=200411221440.21131.vladimir.vorobyov@iss.org.ua \
    --to=vladimir.vorobyov@iss.org.ua \
    --cc=drow@false.org \
    --cc=gdb@sources.redhat.com \
    --cc=schwab@suse.de \
    /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