From: Niu Liang-yong-A16450 <A16450@motorola.com>
To: Balarama Krishna <balaram@samsung.com>
Cc: gdb@sources.redhat.com
Subject: RE: Problem using gdbserver
Date: Fri, 29 Aug 2003 08:22:00 -0000 [thread overview]
Message-ID: <89DEFCC5DB33D411A27F00508BCF8A820FE1D7E3@ZCH07EXM05.corp.mot.com> (raw)
gdb@sources.redhat.com
I can debug is on Linux pc, the issue ocurres on solaris
BR
-----Original Message-----
From: Balarama Krishna [mailto:balaram@samsung.com]
Sent: 2003年8月28日 19:04
To: Niu Liang-yong-A16450
Subject: Re: Problem using gdbserver
> When I want to debug a file, but things happen:
>
> GNU gdb 5.0
> Copyright 2000 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 "sparc-sun-solaris2.7".
> (gdb) file filegen
> Reading symbols from filegen...done.
> (gdb) run
> Starting program: /home/a16450/filegen/filegen
> chdir: Too many arguments.
>
> Program exited with code 01.
> You can't do that without a process to debug.
>
>
The problem may be with the application, as "chdir" failed, not with the
gdb.
Regards,
Balaram.
next reply other threads:[~2003-08-29 8:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-29 8:22 Niu Liang-yong-A16450 [this message]
2003-08-29 9:43 ` Satheesha.T.N
2003-08-29 13:55 ` Daniel Jacobowitz
-- strict thread matches above, loose matches on Subject: below --
2003-08-28 11:00 Niu Liang-yong-A16450
2003-08-26 14:14 Help Needed: set up GDB Remote Debugger (arm-linux) Balarama Krishna
2003-08-26 14:17 ` Daniel Jacobowitz
2003-08-28 6:58 ` Problem using gdbserver Balarama Krishna
2003-08-28 10:51 ` Balarama Krishna
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=89DEFCC5DB33D411A27F00508BCF8A820FE1D7E3@ZCH07EXM05.corp.mot.com \
--to=a16450@motorola.com \
--cc=balaram@samsung.com \
--cc=gdb@sources.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