From: Daniel Jacobowitz <drow@mvista.com>
To: Ming Sun <mings@intellambda.com>
Cc: gdb@sources.redhat.com
Subject: Re: more info on Help needed for gdbserver on redhat 9, thanks!
Date: Tue, 07 Oct 2003 01:25:00 -0000 [thread overview]
Message-ID: <20031007012549.GA17964@nevyn.them.org> (raw)
In-Reply-To: <3F821438.2020004@intellambda.com>
On Mon, Oct 06, 2003 at 06:17:44PM -0700, Ming Sun wrote:
> After changed to static linking without share liberies. The gdbserver works
> for the test program. But my real program cannot work with static library
> due to different thread behave. Does anyone know why dynamic library
> causes SEGSEGV in gdbserver? By the way, I check /usr/lib/libglib* on
> both PCs. All files have same size and date.
Your two hosts do not have the same libraries.
Either make sure that they do, or else use set solib-absolute-prefix;
copy the target's library layout to the host and point GDB at it before
connecting.
>
> Thanks,
>
> Ming
>
> ===========================================================================
>
> I got two PCs. One is running target and run gdbserber and the other is
> host and run
> gdb. Both are redhat 9. I am constantly get SIGSEGV before it reaches
> main().
> Gdb works fine in local machine. Does anyone know what is my problem?
> Thanks in advance for your help!
>
> Ming
>
> Here are the outputs from both target and host.
>
> ==============TARGET==============
> root@pc28 x86]# gdbserver foo:5432 test
> Process test created; pid = 3569
> Remote debugging from host 192.168.0.57
>
>
> ==============HOST==============
>
> [root@mings x86]# gdb test
> GNU gdb Red Hat Linux (5.3post-0.20021129.18rh)
> Copyright 2003 Free Software Foundation, Inc.
> GDB is free software, covered by the GNU General Public License, and you are
> welcome to change it and/or distribute copies of it under certain
> conditions.
> Type "show copying" to see the conditions.
> There is absolutely no warranty for GDB. Type "show warranty" for details.
> This GDB was configured as "i386-redhat-linux-gnu"...
> (gdb) target remote 192.168.0.155:5432
> Remote debugging using 192.168.0.155:5432
> 0x40000c10 in ?? ()
> (gdb) symbol-file test
> Load new symbol table from "test"? (y or n) y
> Reading symbols from test...done.
> (gdb) list main
> 1 #include <stdio.h>
> 2
> 3 main (int argc,
> 4 char *argv[])
> 5 {
> 6 printf ("test gdbserver\n");
> 7 }
> (gdb) br main
> Breakpoint 1 at 0x8048338: file test.c, line 6.
> (gdb) c
> Continuing.
>
> Program received signal SIGSEGV, Segmentation fault.
> 0x0c011ad7 in ?? ()
> (gdb) where
> #0 0x0c011ad7 in ?? ()
> #1 0x40001365 in ?? ()
> #2 0x4000eebf in ?? ()
> #3 0x40000f53 in ?? ()
> (gdb) quit
> The program is running. Exit anyway? (y or n) y
> [root@mings x86]# gcc -v
> Reading specs from /usr/lib/gcc-lib/i386-redhat-linux/3.2.2/specs
> Configured with: ../configure --prefix=/usr --mandir=/usr/share/man
> --infodir=/usr/share/info --enable-shared --enable-threads=posix
> --disable-checking --with-system-zlib --enable-__cxa_atexit
> --host=i386-redhat-linux
> Thread model: posix
> gcc version 3.2.2 20030222 (Red Hat Linux 3.2.2-5)
>
>
--
Daniel Jacobowitz
MontaVista Software Debian GNU/Linux Developer
next prev parent reply other threads:[~2003-10-07 1:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 1:20 Ming Sun
2003-10-07 1:25 ` Daniel Jacobowitz [this message]
[not found] ` <3F84C42F.5080006@intellambda.com>
2003-10-09 2:18 ` 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=20031007012549.GA17964@nevyn.them.org \
--to=drow@mvista.com \
--cc=gdb@sources.redhat.com \
--cc=mings@intellambda.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