Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Chris Faylor <cgf@cygnus.com>
To: Eli Zaretskii <eliz@is.elta.co.il>
Cc: toddpw@windriver.com, gdb@sourceware.cygnus.com
Subject: Re: Readline and -DMINIMAL
Date: Fri, 31 Mar 2000 18:28:00 -0000	[thread overview]
Message-ID: <20000331212807.A2696@cygnus.com> (raw)
Message-ID: <20000331182800.ElrLg8zJyogtgfdMgOADEKkcXUqimVz-jQVe5RM-GSA@z> (raw)
In-Reply-To: <200003312329.SAA07193@indy.delorie.com>

On Fri, Mar 31, 2000 at 06:29:30PM -0500, Eli Zaretskii wrote:
>> The readline directory in CVS is version
>> 4.0 with changes from Eli Zaretskii (I hope he also notified the readline
>> maintainer about these) to get things working on DJGPP.
>
>I checked my patches against the recent beta version of Readline, and
>all the changes are already taken care of there (the person who ported
>Bash to DJGPP submitted almost identical patches to the Readline
>maintainer).

That's good to hear.  I guess we should think about importint the newest readline
sometime after 5.0 branches.

cgf
From cgf@cygnus.com Fri Mar 31 18:29:00 2000
From: Chris Faylor <cgf@cygnus.com>
To: David Williams <davidwilliams@ozemail.com.au>
Cc: Serge Nikulin <nikulin@actsw.amat.com>, gdb@sourceware.cygnus.com
Subject: Re: How to set RS232 speed in gdb in WinNT?
Date: Fri, 31 Mar 2000 18:29:00 -0000
Message-id: <20000331212950.B2696@cygnus.com>
References: <003e01bf9b69$afc0c220$35758798@mis.amat.com> <38E538DF.ED6289D6@ozemail.com.au>
X-SW-Source: 2000-03/msg00390.html
Content-length: 1359

On Sat, Apr 01, 2000 at 09:46:40AM +1000, David Williams wrote:
>Use -b command line option to change baud rate
>
>eg.     gdb -b 115200
>to set baud rate 115200 baud.
>Dave.

Note that in some older versions of the Cygwin DLL (possibly in B20.1)
there was an error which caused the 115200 baud rate to be incorrectly
handled.  Everything should work ok if you are using the Cygwin CD or if
you are using a later cygwin snapshot.

cgf

>Serge Nikulin wrote:
>> I use gdb for remote debugging of m68k target, compiled with MRI
>> <--host=i686-pc-cygwin32 --target=m68k-motorola-ieee>
>> Native MRI' X-Ray debugger does not support our home-made RTOS.
>> GDB works but I have few questions.
>>
>> 1) Currently ieee-695 bfd section is not connected to gdb, so I work without
>> src.
>>     I've checked examples of coff and aout conections and it does not look
>> as a 1-day job for me
>>     (including the fact that ieee-695 support in bfd is incomplete).
>>     Does anyone have ieee + gdb experience?
>>
>> 2) In my gdb session under WinNT I use command "target remote com1"
>> In this case gdb connects to COM1 at 9600 baud. I'd like to change this
>> speed (say, to 38400) but I can't. I've changed default speed for COM1 in
>> WinNT's control panel but it did not help. It looks like I have to pass that
>> speed to cygwin.dll somehow. How can I do that?
From ac131313@cygnus.com Sat Apr 01 17:13:00 2000
From: Andrew Cagney <ac131313@cygnus.com>
To: GDB Discussion <gdb@sourceware.cygnus.com>, GDB Patches <gdb-patches@sourceware.cygnus.com>
Subject: GDB five branch - tuesday GMT?
Date: Sat, 01 Apr 2000 17:13:00 -0000
Message-id: <38E69E5D.B67C1941@cygnus.com>
X-SW-Source: 2000-04/msg00000.html
Content-length: 199

[Reply-to: set to gdb-patches]

Looking at what is still outstanding, and assuming I get back positive
e-mails, I think it will be possible to cut the GDB 5 branch around
Tuesday lunch GMT.

	Andrew
From Philip.Blundell@pobox.com Sun Apr 02 12:46:00 2000
From: Philip Blundell <Philip.Blundell@pobox.com>
To: scottb@netwinder.org
Cc: gdb@sourceware.cygnus.com
Subject: gdb build fails for i586-linux cross arm-linux
Date: Sun, 02 Apr 2000 12:46:00 -0000
Message-id: <E12bqKZ-0005uP-00@kings-cross.london.uk.eu.org>
X-SW-Source: 2000-04/msg00001.html
Content-length: 1144

Hi Scott

Compiling the current GDB on my Intel machine with `--target=arm-linux', I 
get:

gcc -g        -o gdb main.o libgdb.a    ../bfd/libbfd.a ../readline/libreadline.a ../opcodes/libopcodes.a  ../libiberty/libiberty.a -lncurses    ../libgui/src/libgui.a -L/var/tmp/build/binutils-arm/itcl/itcl/unix -litcl3.0 -L/var/tmp/build/binutils-arm/itcl/itk/unix -litk3.0 -L/var/tmp/build/binutils-arm/tix/unix/tk8.0 -ltix4.1.8.0 -L/var/tmp/build/binutils-arm/tk/unix -ltk8.0 -L/var/tmp/build/binutils-arm/tcl/unix -ltcl8.0   -L/usr/X11R6/lib -lX11 -ldl  -lieee -lm -lm  ../libiberty/libiberty.a  -ldl -rdynamic
libgdb.a(values.o): In function `value_being_returned':
/usr/src/sourceware/src/gdb/values.c:1542: undefined reference to `arm_linux_extract_return_value'
libgdb.a(infrun.o): In function `handle_inferior_event':
/usr/src/sourceware/src/gdb/infrun.c:2296: undefined reference to `arm_get_longjmp_target'

These functions are defined in arm-linux-nat.c but required by 
config/arm/tm-linux.h.  Should we create a new arm-linux-tdep.c file for these 
functions, or are they genuinely not useful outside a native environment?

Thanks

p.



       reply	other threads:[~2000-03-31 18:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200003281230.EAA15638@alabama.wrs.com>
     [not found] ` <20000328105123.G27306@cygnus.com>
     [not found]   ` <200003312329.SAA07193@indy.delorie.com>
2000-04-01  0:00     ` Chris Faylor [this message]
2000-03-31 18:28       ` Chris Faylor

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=20000331212807.A2696@cygnus.com \
    --to=cgf@cygnus.com \
    --cc=eliz@is.elta.co.il \
    --cc=gdb@sourceware.cygnus.com \
    --cc=toddpw@windriver.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