From: Jitendra kanitkar <Jitendrak@netbrahma.com>
To: "'ecos-discuss@sources.redhat.com'" <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] Help: Linux Synthetic target
Date: Thu, 01 Mar 2001 00:50:00 -0000 [thread overview]
Message-ID: <13D467F625FAD511AE2A00D0B7B917D7089D34@BRAHMA01> (raw)
-thanks
Jitendra
Hi there,
Thanks Jesper. using native gdb my current work will be over. No problems.
But I am feeling like using ecos. For just sake of satisfaction can anybody
pl. explain what is happening if i386-elf-gdb gives error(don't know how to
run) and native gdb works in case Linux Synthetic target.
Thanks in advance,
Jitendra..
> >>>>> "Jitendra" == Jitendra kanitkar <Jitendrak@netbrahma.com> writes:
>
> Jitendra> If I run threa_gdb.exe with gdb only then it runs it
> Jitendra> properly. Any pointers on this?
>
> Yes, use your native GDB only.
>
> Jesper
>
next reply other threads:[~2001-03-01 0:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-01 0:50 Jitendra kanitkar [this message]
2001-03-01 1:21 ` Jesper Skov
-- strict thread matches above, loose matches on Subject: below --
2001-02-28 4:26 Jitendra kanitkar
2001-02-28 5:24 ` Jesper Skov
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=13D467F625FAD511AE2A00D0B7B917D7089D34@BRAHMA01 \
--to=jitendrak@netbrahma.com \
--cc=ecos-discuss@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).