From: Pedro Alves <pedro@codesourcery.com>
To: gdb@sourceware.org
Cc: Jusctsch <schumjs@gmail.com>
Subject: Re: Thread exit error : gdb7.2 in FreeBSD (built from ports)
Date: Wed, 14 Sep 2011 17:59:00 -0000 [thread overview]
Message-ID: <201109141859.20945.pedro@codesourcery.com> (raw)
In-Reply-To: <32465344.post@talk.nabble.com>
Please don't top post.
On Wednesday 14 September 2011 18:12:06, Jusctsch wrote:
>
> Sure,
> I am running on FreeBSD, and they pull vanilla source and apply their
> patches to it. In addition, I had written a patch on my own which is
> removing an error check in get_current_frame on thread exit and running into
> an issue later on. I'm disregarding the fatal errors in the previous post
> and focusing on the "invalid thread" issue. With just the FreeBSD patches
> applied on gdb7.2, I boot up my application and see the following:
>
> =thread-created,id="60",group-id="i1"
> ~"[New Thread 803855740 (LWP 100223)]\n"
> *running,thread-id="all"
> =thread-created,id="61",group-id="i1"
> ~"[New Thread 82b055500 (LWP 100235)]\n"
> *running,thread-id="all"
> ~"[Thread 82b055c00 (LWP 100221 FooTask) exited]\n"
> =thread-exited,id="58",group-id="i1"
> &"/tmp/.gdbinit:4: Error in sourced command file:\n"
> &"Invalid selected thread.\n"
> (gdb)
I understand that the whole program exited, and you're getting
that error from withing get_current_frame, right? Please give
me the most detail as possible so that I don't have to try
to guess things.
Why is GDB calling get_current_frame at all? Please show the
same but with "set debug infrun 1". Sounds like a FreeBSD
backend bug.
--
Pedro Alves
next prev parent reply other threads:[~2011-09-14 17:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-14 14:27 Jusctsch
2011-09-14 14:41 ` Jusctsch
2011-09-14 15:04 ` Pedro Alves
2011-09-14 17:12 ` Jusctsch
2011-09-14 17:59 ` Pedro Alves [this message]
2011-09-22 15:49 ` Jusctsch
2011-09-22 16:34 ` Jusctsch
2011-09-22 17:11 ` Pedro Alves
[not found] ` <CAJoUm=HvAjAQVMVPEWs=deg0h6-m9+oMK3frD2_=bHRx+J1s5g@mail.gmail.com>
2011-09-23 19:31 ` John Schumacher
2011-09-22 22:30 John Schumacher
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=201109141859.20945.pedro@codesourcery.com \
--to=pedro@codesourcery.com \
--cc=gdb@sourceware.org \
--cc=schumjs@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).