I meet the same problem.
When remove the putty "R1234 ip.of.linux.machine:1234" setting,
./arm-eabi-gdb
(gdb) target remote remote:1234
remote:1234: Connection refused.
Why about it ?
Thanks!
I have launch the gdbserver on emulator like,
./gdbserver :3050 -attch:995
gdbserver :3050 --attach 995
Attached; pid = 995
Listening on port 3050
and run adb forward tcp:1234 tcp:3050 on windows
netstat -aon
On Sep 8, 2:16 pm, Pan <
pan.gaoy...@gmail.com> wrote:
> Great, I verified your suggestion works fine
>
> Could anyone tell me what the below warning means?
>
> GNUgdb6.6
> Copyright (C) 2006 Free Software Foundation, Inc.GDBis 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 forGDB. Type "show warranty" for
> details.
> ThisGDBwas configured as "--host=i686-pc-linux-gnu --target=arm-elf-
> linux"...
> (gdb) set solib-search-path out/target/product/generic/symbols/system/
> lib
> (gdb) set solib-absolute-prefix out/target/product/generic/symbols
> (gdb) target remote :1234
> Remote debugging using :1234
> warning: Unable to find dynamic linker breakpoint function.GDBwill be unable to debug shared library initializers
> and track explicitly loaded dynamic code.
>
> On Sep 7, 9:22 pm, Freepine <
freep...@gmail.com> wrote:
>
> > Shouldn't the tunnel setting in putty be R1234 -> localhost:1234?Then the
> > debug session can be established from remote Linux machine:1234 -> Windows
> > host port 1234 ->emulator/device:1234.
>
> > On Mon, Sep 7, 2009 at 9:51 AM, Pan <
pan.gaoy...@gmail.com> wrote:
>
> > > Hi,
>
> > > I have the emulator running on my windows, and a Linux is used to
> > > build the entireAndroidplatform code. Here is what I tried to debug
> > > the native code with my emulator, please help verify what is wrong
>
> > > launch the gdbserver on emulator like,
>
> > > ./gdbserver :3050 ./hello
>
> > > run adb forward tcp:1234 tcp:3050 on windows, then check the forward
> > > result, I can see it is listening on my windows localhost,
>
> > > TCP
127.0.0.1:1234 0.0.0.0:0 LISTENING
>
> > > I need to run armgdbon a remote Linux machine, so a ssh tunnel is