Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Shaun Jackman <shaunj@gray-interfaces.com>
To: gdb@sources.redhat.com
Subject: RDI over ethernet failure message
Date: Wed, 01 Nov 2000 09:12:00 -0000	[thread overview]
Message-ID: <00110110123200.14774@ed> (raw)

The RDI over ethernet failure message should be a little more user friendly.
Also, it shouldn't exit gdb if it's unable to connect.

GNU gdb 5.0
[clip]
This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
(gdb) ta rdi e=192.168.1.99
Fatal error: ethernet send failure [Invalid argument]
[gdb exits]


The serial RDI message makes a lot more sense.

GNU gdb 5.0
[clip]
This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
(gdb) ta rdi /dev/ttyS0
RDI_open: undefined error message, should reset target
RID_open failed
(gdb)

-- 
Shaun
From tromey@cygnus.com Wed Nov 01 09:15:00 2000
From: Tom Tromey <tromey@cygnus.com>
To: gdb@sourceware.cygnus.com
Subject: Re: Subscribe gdb-prs@sources.redhat.com to gdb@sources.redhat.com?
Date: Wed, 01 Nov 2000 09:15:00 -0000
Message-id: <87wvenaa0r.fsf@creche.cygnus.com>
References: <20001031221747.A32231@redhat.com> <39FFA8A8.5B3C13D0@cygnus.com> <20001101003352.A13485@redhat.com>
X-SW-Source: 2000-11/msg00005.html
Content-length: 301

Chris> I believe that replies would end up in the PR but I don't know
Chris> for sure.

Ordinarily you have to CC the `-gnats' address to get the message in
the PR.  Unfortunately sometimes Gnats sends out a message to (eg)
gdb-prs@... and then if you reply to all you don't CC gdb-gnats.

Tom
From fnasser@cygnus.com Wed Nov 01 09:40:00 2000
From: Fernando Nasser <fnasser@cygnus.com>
To: shaunj@gray-interfaces.com
Cc: gdb@sources.redhat.com
Subject: Re: RDI over ethernet failure message
Date: Wed, 01 Nov 2000 09:40:00 -0000
Message-id: <3A005585.8613BE17@cygnus.com>
References: <00110110123200.14774@ed>
X-SW-Source: 2000-11/msg00006.html
Content-length: 991

Shaun,

I don't have any hardware that talks RDI over Ethernet arounf here,
so I cannot reproduce the situation nor test any changes.

Won't you consider submitting a patch yourself?

Regards,
Fernando


Shaun Jackman wrote:
> 
> The RDI over ethernet failure message should be a little more user friendly.
> Also, it shouldn't exit gdb if it's unable to connect.
> 
> GNU gdb 5.0
> [clip]
> This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
> (gdb) ta rdi e=192.168.1.99
> Fatal error: ethernet send failure [Invalid argument]
> [gdb exits]
> 
> The serial RDI message makes a lot more sense.
> 
> GNU gdb 5.0
> [clip]
> This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
> (gdb) ta rdi /dev/ttyS0
> RDI_open: undefined error message, should reset target
> RID_open failed
> (gdb)
> 
> --
> Shaun

-- 
Fernando Nasser
Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
2323 Yonge Street, Suite #300
Toronto, Ontario   M4P 2C9
From sjackman@pathwayconnect.com Wed Nov 01 10:06:00 2000
From: Shaun Jackman <sjackman@pathwayconnect.com>
To: Fernando Nasser <fnasser@cygnus.com>
Cc: shaunj@gray-interfaces.com, gdb@sources.redhat.com
Subject: Re: RDI over ethernet failure message
Date: Wed, 01 Nov 2000 10:06:00 -0000
Message-id: <Pine.LNX.4.21.0011011047360.14868-100000@ed.gray.internal>
References: <3A005585.8613BE17@cygnus.com>
X-SW-Source: 2000-11/msg00007.html
Content-length: 1339

I'd be more than happy to. I've never contributed to a GNU project
before though. Could you point me to a "new contributors" faq?
Is it reasonable to diff against gdb-5.0 or do I need go to CVS?

Cheers,
Shaun


On Wed, 1 Nov 2000, Fernando Nasser wrote:

> Shaun,
> 
> I don't have any hardware that talks RDI over Ethernet arounf here,
> so I cannot reproduce the situation nor test any changes.
> 
> Won't you consider submitting a patch yourself?
> 
> Regards,
> Fernando
> 
> 
> Shaun Jackman wrote:
> > 
> > The RDI over ethernet failure message should be a little more user friendly.
> > Also, it shouldn't exit gdb if it's unable to connect.
> > 
> > GNU gdb 5.0
> > [clip]
> > This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
> > (gdb) ta rdi e=192.168.1.99
> > Fatal error: ethernet send failure [Invalid argument]
> > [gdb exits]
> > 
> > The serial RDI message makes a lot more sense.
> > 
> > GNU gdb 5.0
> > [clip]
> > This GDB was configured as "--host=i586-pc-linux-gnu --target=arm-elf"...
> > (gdb) ta rdi /dev/ttyS0
> > RDI_open: undefined error message, should reset target
> > RID_open failed
> > (gdb)
> > 
> > --
> > Shaun
> 
> -- 
> Fernando Nasser
> Red Hat Canada Ltd.                     E-Mail:  fnasser@redhat.com
> 2323 Yonge Street, Suite #300
> Toronto, Ontario   M4P 2C9
> 
> 
> 


             reply	other threads:[~2000-11-01  9:12 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-01  9:12 Shaun Jackman [this message]
     [not found] <Pine.LNX.4.21.0011011047360.14868-100000@ed.gray.internal>
2000-11-01 10:21 ` Fernando Nasser

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=00110110123200.14774@ed \
    --to=shaunj@gray-interfaces.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