Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: "H . J . Lu" <hjl@lucon.org>
Cc: GDB <gdb@sourceware.cygnus.com>
Subject: Re: PATCH: Re: [RFHelp] Linux, threads, and regsets in thread_db
Date: Sat, 03 Nov 2001 14:25:00 -0000	[thread overview]
Message-ID: <20011115114841.A5118@nevyn.them.org> (raw)
In-Reply-To: <20011114134521.A25645@lucon.org>

On Wed, Nov 14, 2001 at 01:45:21PM -0800, H . J . Lu wrote:
> On Wed, Oct 03, 2001 at 09:10:07PM -0400, Daniel Jacobowitz wrote:
> > > > 
> > > 
> > > How far have you gone on Linux/mips? I know gdb 5.1 doesn't work with
> > > threads on Linux/mips. Does your change fix it? I'd like to clean up
> > > glibc for mips on this.
> > 
> > Yes.  Debugging threads works reasonably well.  I'm going to do more
> > work about this in the next couple of months too, I think; after I go
> > back to gdbserver for a little while.
> 
> I am still having problems with threads on mips. I cannot set break
> point after target has run:
> 
> (gdb) run
> ...
> (gdb) b main
> reading register sp (#29): No such process.
> 
> The problem is gdb tries to read sp register in thread mode. This patch
> seems to work for me.

This should not be a problem.  It works fine for me.  I'll step through
it later tonight and try to figure out what the difference is from what
you're seeing.

> Another problem is when I set a break point in a thread function, only
> the first thread stops. I got
> 
> (gdb) b process
> Breakpoint 1 at 0x400a38: file Examples/ex1.c, line 14.
> (gdb) r
> Starting program: /export/build/gnu/glibc/build-mipsel-linux/linuxthreads/ex1 
> [New Thread 1024 (LWP 26552)]
> [New Thread 2049 (LWP 26569)]
> [New Thread 1026 (LWP 26570)]
> [Switching to Thread 1026 (LWP 26570)]
> 
> Breakpoint 1, process (arg=0x1000) at Examples/ex1.c:14
> 14        fprintf (stderr, "Starting process %s\n", (char *) arg);
> ...
> Program received signal SIGTRAP, Trace/breakpoint trap.
> [Switching to Thread 1024 (LWP 26552)]
> 0x2ab8de24 in __syscall_rt_sigsuspend () at soinit.c:56
> 56      soinit.c: No such file or directory.
> 
> But it may be a kernel bug.

Something is suspicious here.  The process in sigsuspend should have
been stopped with SIGSTOP, not SIGTRAP...  is this an example program
from glibc?

> H.J.
> ---
> 2001-11-14  H.J. Lu  (hjl@gnu.org)
> 
> 	* mips-tdep.c (heuristic_proc_desc): Read register only when
> 	target is running.

I can't see why this changes behavior in the way you're seeing.  I'm
pretty sure it isn't right.


-- 
Daniel Jacobowitz                           Carnegie Mellon University
MontaVista Software                         Debian GNU/Linux Developer


  reply	other threads:[~2001-11-15 16:48 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-24 18:27 Daniel Jacobowitz
2001-09-25  3:09 ` Mark Kettenis
     [not found] ` <20011003170848.A30843@lucon.org>
     [not found]   ` <20011003211007.A12210@nevyn.them.org>
2001-11-03 12:32     ` PATCH: " H . J . Lu
2001-11-03 14:25       ` Daniel Jacobowitz [this message]
2001-11-03 16:54         ` H . J . Lu
2001-11-06 14:28           ` 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=20011115114841.A5118@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sourceware.cygnus.com \
    --cc=hjl@lucon.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