Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Daniel Jacobowitz <drow@mvista.com>
To: Paul Mundt <paul.mundt@timesys.com>
Cc: gdb@sources.redhat.com
Subject: Re: SIG32/SIGTRAP issues
Date: Wed, 04 Dec 2002 10:44:00 -0000	[thread overview]
Message-ID: <20021204184526.GA25681@nevyn.them.org> (raw)
In-Reply-To: <1039030436.11722.76.camel@Origin>

On Wed, Dec 04, 2002 at 02:33:57PM -0500, Paul Mundt wrote:
> Hi,
> 
> On Tue, 2002-12-03 at 18:24, Daniel Jacobowitz wrote:
> > Funny, no one reports this for months and this is the third report I've
> > seen in a week...  At the bottom of this message is a workaround.  I'm
> > not proposing it be committed, since it's obviously pretty gross.  The
> > real issue is the concept of thread_stratum and core_stratum as
> > separate from process_stratum.  I don't think it's appropriate - if we
> > are debugging a core and process at the same time this isn't how it
> > should work.  This ties in to all the make-targets-a-real-stack thing -
> > I'm not entirely convinced on that score either.
> 
> Okay, making progress. This takes care of the SIG32/SIGTRAP issues,
> though now it looks like PPC is stuck on SIG33 issues.
> 
> Running the same test-case from yesterday, if I run the shared version
> twice in a row, gdb segfaults. If I run the shared or static version of
> the app under gdb under gdb, I get SIG33 (which occurs in different
> locations per-thread if its static).

SIG33 is CANCEL.  Lin-lwp should be reporting it as such.  Do you have
__pthread_sig_cancel in your library?  Is check_thread_signals working?


> (top-gdb) bt
> Reading in symbols for ../../package/gdb/dbxread.c...done.
> Reading in symbols for ../../package/gdb/elfread.c... and
> ../../package/gdb/solib-svr4.c...done.
> Reading in symbols for ../../package/gdb/solib.c...done.
> #0  0x0fe04b08 in strchr () from /lib/libc.so.6
> #1  0x1010597c in end_psymtab (pst=0x106f5ea0, include_list=0x7fffe910,
> num_includes=1, capping_symbol_offset=-16843009,
> capping_text=2139062143,
>     dependency_list=0x7fffe880, number_dependencies=0,
> textlow_not_set=1) at ../../package/gdb/dbxread.c:2253
> #2  0x10104a40 in read_dbx_symtab (objfile=0x104e4a88) at
> ../../package/gdb/dbxread.c:1524

Dunno about this one, try a newer GDB maybe.

-- 
Daniel Jacobowitz
MontaVista Software                         Debian GNU/Linux Developer


      reply	other threads:[~2002-12-04 18:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-03 14:52 Paul Mundt
2002-12-03 15:24 ` Daniel Jacobowitz
2002-12-03 15:30   ` H. J. Lu
2002-12-03 15:43     ` Daniel Jacobowitz
2002-12-03 15:58       ` H. J. Lu
2002-12-03 15:52   ` Andrew Cagney
2002-12-03 15:58     ` Daniel Jacobowitz
2002-12-03 16:09       ` H. J. Lu
2002-12-04 10:30   ` Paul Mundt
2002-12-04 10:44     ` Daniel Jacobowitz [this message]

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=20021204184526.GA25681@nevyn.them.org \
    --to=drow@mvista.com \
    --cc=gdb@sources.redhat.com \
    --cc=paul.mundt@timesys.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