Changeset 60ee6da in rtems


Ignore:
Timestamp:
Aug 2, 1999, 4:38:28 PM (22 years ago)
Author:
Joel Sherrill <joel.sherrill@…>
Branches:
4.10, 4.11, 4.8, 4.9, 5, master
Children:
26eff5c
Parents:
ae2ddb8
Message:

Updated DDD section after comments from Jiri.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/FAQ/freesw.t

    rae2ddb8 r60ee6da  
    3939
    4040By far the easiest way to use DDD if you are on a Redhat Linux system is
    41 to retrieve the latest RPM package. I got mine from
    42 ftp://ftp.crc.ca/systems/linux/redhat/contrib.redhat.com/libc6/i386/ddd-dynamic-
    43 3.1.5-1.i386.rpm.
    44 This particular one is for Redhat 6.0 on i386. For 5.2, I guess you
    45 should use libc5 instead of libc6.
     41to retrieve the RPM package for your OS version.  In general, it is
     42easier to install a static binary since doing so avoids all problems
     43with dynamic library versions.
    4644
    47 You also need Lesstif 0.88. I got mine from
    48 ftp://ftp.hungry.com/pub/hungry/lesstif/bindist/lesstif-0.88.1-1.i386.rpm
     45Some versions of DDD have had trouble with Lesstif.  If you
     46are using Lesstiff, you will need version 0.88 or newer.  It
     47is also available as an RPM at the popular sites.  Another Motif
     48clone is Motive and versions 1.2 and newer known to work with DDD
     49on popular distributions of Linux including RedHat and Slackware.
    4950
    50 Installed as RPMs, DDD and Lesstif work out-of-the-box.
     51Installed as RPMs, DDD in conjunction with either Lesstif or Motive
     52should work out-of-the-box.
    5153
    52 Both Lesstif and DDD can be built from scratch without any problems.
    53 
    54 The isntruction on how to install Lesstif are at
    55 http://www.cs.tu-bs.de/softech/ddd/.  They indicate that
     54User comments indicate that both Lesstif and DDD can be built
     55from scratch without any problems.  Instructions on installing
     56Lesstif are at http://www.cs.tu-bs.de/softech/ddd/.  They
     57indicate that
    5658
    5759@itemize @bullet
     
    7173library paths to point to the Motif 1.2 library.
    7274
    73 The student configure DDD --with-motif-libraries=/usr/local/lib
    74 --with-motif-includes=/usr/local/include
     75The following notes are from an RTEMS user who uses DDD in conjunction
     76with Lesstif.  Configure DDD "--with-motif-libraries=/usr/local/lib
     77--with-motif-includes=/usr/local/include" DDD needs gnuplot 3.7. 
     78ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot-3.7.tar.gz. Build and
     79install from scratch. 
    7580
    76 You will need gnuplot 3.7. I got mine from
    77 ftp://ftp.dartmouth.edu/pub/gnuplot/gnuplot-3.7.tar.gz. Build and
    78 install from scratch.
    79 
    80 I start DDD from a script in $HOME/bin:
     81DDD can be started from a script that specifies the cross debugger.
     82This simplifies the invocation.  The following example shows what
     83a script doing this looks like.
    8184
    8285@example
     
    8588@end example
    8689
     90Under many flavors of UNIX, you will likely have to relax permissions.
    8791
    88 Now for the hard part:
    89 
    90 under RH Linux, to get gdb to use the serial ports while running as a
    91 mere mortal, edit /etc/security/console.perms, and create a <serial>
     92On Linux, to get gdb to use the serial ports while running as a
     93normal user, edit /etc/security/console.perms, and create a <serial>
    9294class (call it whatever you want).
    9395
     
    103105@end example
    104106
    105 And voila!
    106 
    107 I use minicom to communicate with the target to initiate a TFTP
    108 download. I then suspend minicom,  lauch DDD, and begin debugging.
     107Users report using minicom to communicate with the target to initiate a TFTP
     108download. They then suspend minicom, launch DDD, and begin debugging.
    109109
    110110The procedure should be the same on other platforms, modulo the choice
    111111of terminal emulator program and the scheme used to access the serial
    112 ports. From the cygwin mailing list, I have the impression that GDB has
    113 some problems communicating over serial lines on that platform.
     112ports. From problem reports on the cygwin mailing list, it appears that
     113GDB has some problems communicating over serial lines on that platform.
    114114
    115 P.S. GDB doesn't like getting lots of input from the program under test
    116 over the serial line. Actually, it doesn't care, but it looses
     115NOTE: GDB does not like getting lots of input from the program under test
     116over the serial line. Actually, it does not care, but it looses
    117117characters. It would appear that flow control is not re-enabled when it
    118118resumes program execution. At times, it looked like the test were
    119119failing, but everything was OK. We modified the MVME167 serial driver to
    120 send test output to another serial port.
     120send test output to another serial port.  Using two serial ports is
     121usually the easiest way to get test output while retaining a reliable debug
     122connection regardless of the debugger/target combination.
    121123
    122124Information provided by Charles-Antoine Gauthier (charles.gauthier@@iit.nrc.ca)
Note: See TracChangeset for help on using the changeset viewer.