From: hjl@lucon.org (H.J. Lu)
To: shebs@cygnus.com (Stan Shebs)
Cc: gdb@cygnus.com, gdb-testers@cygnus.com, gdb-patches@cygnus.com
Subject: Re: GDB in CVS!
Date: Fri, 16 Apr 1999 09:08:00 -0000 [thread overview]
Message-ID: <m10YAcv-000ErMC@ocean.lucon.org> (raw)
Message-ID: <19990416090800.TW_4lTUiaL74jL88rA5LpG1c6lxbhj5q8yJhhhbNH_I@z> (raw)
In-Reply-To: <199904160204.TAA10683@andros.cygnus.com>
>
> cvs -z 9 -d :pserver:anoncvs@sourceware.cygnus.com:/cvs/gdb login
> {enter "anoncvs" as the password}
> cvs -z 9 -d :pserver:anoncvs@sourceware.cygnus.com:/cvs/gdb co gdb
>
> Please let me know asap if anything goes wrong with this. Have fun!
>
Does anyone see this?
....
U gdb/gdb/symm-nat.c
U gdb/gdb/symm-tdep.c
U gdb/gdb/symmisc.c
cvs [server aborted]: unable to reopen `/cvs/gdb/gdb/gdb/symtab.c,v'
--
H.J. Lu (hjl@gnu.org)
From philb@gnu.org Fri Apr 16 15:46:00 1999
From: Philip Blundell <philb@gnu.org>
To: christophe leroy <leroy@ensea.fr>
Cc: gdb@cygnus.com
Subject: Re: Unknown error with gdb [tcsetpgrp failed in terminal_inferior: Inappropriate ioctl for device]
Date: Fri, 16 Apr 1999 15:46:00 -0000
Message-id: <E10YGBG-0007Tj-00@kings-cross.london.uk.eu.org>
References: <37176E57.48332685@ensea.fr>
X-SW-Source: 1999-04/msg00046.html
Content-length: 342
>Does someone knows why I'm getting such an error when triing to run
>something with gdb on an arm processor :
Try gdb 4.18 with the patch I posted to this mailing list a few days ago. You
need to be running a 2.2.5 kernel patched with the latest diff from my
directory on ftp.netwinder.org for native breakpoints to work, though.
p.
next prev parent reply other threads:[~1999-04-16 9:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-04-15 19:05 Stan Shebs
1999-04-15 20:05 ` Brendan Simon
1999-04-19 12:23 ` Stan Shebs
1999-04-16 8:35 ` H.J. Lu [this message]
1999-04-16 9:08 ` H.J. Lu
[not found] <199904160204.TAA10683.cygnus.gdb@andros.cygnus.com>
1999-04-15 20:27 ` DJ Delorie
1999-04-15 21:08 ` DJ Delorie
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=m10YAcv-000ErMC@ocean.lucon.org \
--to=hjl@lucon.org \
--cc=gdb-patches@cygnus.com \
--cc=gdb-testers@cygnus.com \
--cc=gdb@cygnus.com \
--cc=shebs@cygnus.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