Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Leon Pollak <leonp@plris.com>
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: gdb@sourceware.org
Subject: Re: Restarting gdbserver
Date: Thu, 20 Jan 2011 14:10:00 -0000	[thread overview]
Message-ID: <201101201615.11787.leonp@plris.com> (raw)

SORRY PLEASE!!!!!
I forgot the backtrace output:
(gdb) bt
#0  0x400314bc in pthread_cond_wait@@GLIBC_2.4 () from 
/opt/FS/lib/libpthread.so.0
#1  0x00000000 in ?? ()



On Thursday January 20 2011, Jan Kratochvil wrote:
> or also:
> 	gdbserver --multi COMM
> 	using `target extended-remote ...' instead.
WOW!!!!!!!!
How could I not find this!!??
1001 of thanks!
Works fine. I start thegdb with:

set sysroot /opt/FS/
set remote exec-file /common/csu
target extended-remote 192.168.50.4:44000
---
The only one problem left for me is that when stopped/broken, the stack frame 
is not presented as it usually is:

(gdb) frame
#0  0x400314bc in pthread_cond_wait@@GLIBC_2.4 () from 
/opt/FS/lib/libpthread.so.0

And nothing else...:-(

Thousands of thanks ahead for the help...
-- 
Leon


             reply	other threads:[~2011-01-20 14:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-20 14:10 Leon Pollak [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-01-20  9:25 Leon Pollak
2011-01-20  9:36 ` Jan Kratochvil
2011-01-20 14:07   ` Leon Pollak
2011-01-20 14:11     ` Jan Kratochvil
2011-01-20 14:55       ` Leon Pollak
2011-01-20 17:29         ` Jan Kratochvil
2011-01-21 22:48           ` Leon Pollak
2011-01-23 13:28             ` Jan Kratochvil
2011-01-23 16:39               ` Leon Pollak
2011-01-23 16:48                 ` Jan Kratochvil
2011-01-23 18:01                   ` Leon Pollak
2011-01-23 18:20                     ` Jan Kratochvil
2011-01-23 18:25                     ` Andreas Schwab

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=201101201615.11787.leonp@plris.com \
    --to=leonp@plris.com \
    --cc=gdb@sourceware.org \
    --cc=jan.kratochvil@redhat.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