Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Thomas Schwinge <tschwinge@gnu.org>,
	 "Alfred M. Szmidt" <ams@gnu.org>,
	 bug-hurd@gnu.org
Subject: Re: GDB HEAD (partly) broken for GNU/Hurd
Date: Thu, 09 Oct 2008 11:55:00 -0000	[thread overview]
Message-ID: <200810091255.17394.pedro@codesourcery.com> (raw)
In-Reply-To: <20081009093424.GN7127@fencepost.gnu.org>

A Thursday 09 October 2008 10:34:24, Thomas Schwinge escreveu:
> Hello!
> 
> Some of the changes that have been installed between gdb_6_8-branch and
> HEAD cause GDB to no longer function properly on GNU/Hurd under certain
> circumstances.
> 
>     tschwinge@zoobar:~/tmp/gdb/HEAD.build $ gdb/gdb ~/tmp/n1/hurd/ext2fs.static
>     GNU gdb 6.8.0.20081008-cvs
>     [...]
>     This GDB was configured as "i386-unknown-gnu0.3"...
>     (gdb) r
>     Starting program: /media/data/home/tschwinge/tmp/n1/hurd/ext2fs.static
>     [New thread 8112.1]
>     [New thread 8112.2]
>     [New thread 8112.3]
>     [New thread 8112.4]
>     [New thread 8112.5]
>     
>     Program received signal SIGSEGV, Segmentation fault.
>     convert_options (argp=0x813f0bc, parent=0x0, parent_index=0, group=0x81712e8, cvt=0x101fad0) at argp.h:579
>     579     argp.h: No such file or directory.
>             in argp.h
> 
>     tschwinge@zoobar:~/tmp/gdb/HEAD.build $ gdb/gdb ~/tmp/n1/hurd/ext2fs.static
>     GNU gdb (GDB) 6.8.50.20081009-cvs
>     [...]
>     (gdb) r
>     Starting program: /media/data/home/tschwinge/tmp/n1/hurd/ext2fs.static
>     Can't fetch registers from thread bogus thread id 1: No such thread
> 
> Both have been built (natively) on the same up-to-date Debian GNU/Hurd
> system.
> 
> For easy reproduction, I can publish the faulting binary.
> 

Could you check what caused the breakage?  It *may* have been the ptid
changes I made, or not.

2008-09-08  Pedro Alves  <pedro@codesourcery.com>

        Use ptid_t.tid to store thread ids instead of ptid_t.pid.

        * gnu-nat.c (inf_validate_procs): If this is the first time we're
        seeing a thread id, extend the main thread's ptid.  If we still
        have pending execs, don't be verbose about new threads.
        (gnu_wait, gnu_resume, gnu_attach, gnu_thread_alive)
        (gnu_pid_to_str, cur_thread, sig_thread_cmd): Adjust.
        * i386gnu-nat.c (gnu_fetch_registers, gnu_store_registers):
        Adjust.

If nothing obvious turns up, could you open up a bug report
with a testcase and instructions, please?

-- 
Pedro Alves


  parent reply	other threads:[~2008-10-09 11:55 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-09  9:37 Thomas Schwinge
2008-10-09 11:47 ` Alfred M. Szmidt
2008-10-09 12:46   ` Commit access for me? (was: GDB HEAD (partly) broken for GNU/Hurd) Thomas Schwinge
2008-10-09 13:21     ` Joel Brobecker
2008-10-09 11:55 ` Pedro Alves [this message]
2008-10-11  2:49   ` GDB HEAD (partly) broken for GNU/Hurd Thomas Schwinge
2008-10-11  2:50     ` Pedro Alves
2008-10-11 17:29       ` Thomas Schwinge
2008-10-11 17:43         ` [PATCH?] " Thomas Schwinge
2008-10-13 16:41           ` Ulrich Weigand
2008-10-13 18:35             ` Pedro Alves
2008-10-14 15:49               ` Thomas Schwinge
2008-10-11 17:47         ` Pedro Alves
2008-10-11 17:49           ` Thomas Schwinge

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=200810091255.17394.pedro@codesourcery.com \
    --to=pedro@codesourcery.com \
    --cc=ams@gnu.org \
    --cc=bug-hurd@gnu.org \
    --cc=gdb@sourceware.org \
    --cc=tschwinge@gnu.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