[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20000823: printing in nsharp

Walker,

Can you try running nsharp inside the debugger to see
if we can get any closer to where the program is dying?

I could also post my binary if we need to see if it is your
configuration tables. My solaris version seems to work fine
for me.

One other thing to check for is that you don't have an extra copy of your
ntrans_spool file in your current working directory, since that will
be used before one in $NAWIPS/tables/ntrans.


Anyhow, launch :

dbx $GEMEXE/nsharp

when you get to the dbx prompt, type "run".

That will let you run the program within the debugger.
When you pull up the print selection, you should get output
on where the program currently is. "where" generally tells us what
routine is involved.

The last thing to check is the time stamps on you $NAWIPS/nprogs/nsharp/source
routines. I have April 30, 1999 as the last update to "print_selection.c".

Steve Chiswell



>From: "Walker Ashley" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200008231732.e7NHWEN02036

>Chiz....
>
>Here is the spool Clint said he used (not the one I sent you):
>
>PostScript File Only : PS File Only | PS
>~
>~
>"ntrans_spool" [Read only] 1 line, 41 characters
>
>It crashes before I see a menu.  I tried to run the debug program after the
>core dump. The program ran and then I typed 'where' at the prompt. It then
>said that the program was not active. Here is the printout when I ran the
>program:
>
>imbat% dbx $GEMEXE/nsharp core
>The major new features of this release relative to 3.1 are
> o  Objective C support.  See `help ObjC'.
> o  Fortran 90 support.  See `help fortran'.
> o  Run Time Checking (RTC) gives information about memory usage.
>     See `help check' and `help showmemuse'.
> o  `whereis -a' shows symbolic name of address.  See `help whereis'.
> o  Support for Pascal's `with' statement.
> o  SPARC V8+ support.  See `help dbxenv' and `help registers'.
> o  Better support for stripped binaries.
> o  One-line descriptions of all commands.  See `help commands'.
> o  Dbx now outputs and accepts the suffixes `U', `L', and `LL' to denote
>     unsigned, long, and long long quantities.
>
>See also `help changes31'.
>The major new features of 3.1 relative to 3.0.1 are
> o  Run Time Checking (RTC) now supports multi-threaded applications.
>     See `help rtcmt'.
> o  `adb' mode.  See `help adb' for details.
> o  Output format control.  See `help dbxenv' under 
>     `output_base' for details.
> o  Array-slicing for C, C++. See `help array-slicing'.
> o  Support for Fortran intrinsic functions.
> o  `print' flags for $[].  See `help ksh expressions'.
> o  Printf-like output format control.  See `help format'.
> o  Support for user-supplied pretty printing functions.  See 
>     `help prettyprint'.
> o  The `runargs' command. See `help runargs'.
>
>See also `help changes301'.
>
>To suppress this message, add the following line to your .dbxrc file:
>
>    dbxenv suppress_startup_message 3.2
>Reading symbolic information for nsharp
>dbx: internal error: can't set auxv, already set!
>dbx: warning: core file header read failed
>Reading symbolic information for rtld /usr/lib/ld.so.1
>Reading symbolic information for libXm.so.4
>Reading symbolic information for libXt.so.4
>Reading symbolic information for libX11.so.4
>Reading symbolic information for libF77.so.3
>Reading symbolic information for libm.so.1
>Reading symbolic information for libc.so.1
>Reading symbolic information for libSM.so.6
>Reading symbolic information for libICE.so.6
>Reading symbolic information for libXext.so.0
>Reading symbolic information for libsocket.so.1
>Reading symbolic information for libnsl.so.1
>Reading symbolic information for libdl.so.1
>Reading symbolic information for libmp.so.2
>(dbx) where                                                                
> 
>dbx: program is not active
>(dbx) exit
>
>Clint did not know why it said that the program was not active. I for sure
>have no clue. Let me know if you need any more info.
>
>thanks,
>Walker
>
>
>----------
>> From: Unidata Support <address@hidden>
>> To: Walker Ashley <address@hidden>
>> Cc: address@hidden
> Subject: 20000823: printing in nsharp 
>> Date: Wednesday, August 23, 2000 11:14 AM
>> 
>> 
>> Walker,
>> 
>> Below you show: ntrans_spool.orig. What is in
>$NAWIPS/tables/ntrans/ntrans_spool?
>> 
>> If tou have a core dump, run:
>> dbx $GEMEXE/nsharp core
>> 
>> Then at the dbx prompt type: where
>> 
>> This will help me know at what point the core dump occurs.
>> 
>> Presumably, you are using the File pull down to chose print.
>> At what point does the core dump occur? Before you see a menu, or
>> after you chose to print?
>> 
>> Steve Chiswell
>> 
>> >From: "Walker Ashley" <address@hidden>
>> >Organization: UCAR/Unidata
>> >Keywords: 200008231444.e7NEiON24146
>> 
>> >Hey Chiz....
>> >
>> >Dr. Rowe and I have run into a little snag when trying to print from
>> >nsharp. Rowe followed the directions found within the nprogs tutorial
>(i.e.
>> >defining a printer location in the $NAWIPS/tables/ntrans/ntrans_spool
>file;
>> >see below for the file). Every time I go to print, I still get a
>> >segmentation fault (core dump). Was wondering if you had any suggestions
>on
>> >how to correct this problem.
>> >
>> >Thanks.....
>> >
>> >Walker Ashley
>> >UNL
>> >
>> >"ntrans_spool.orig" [Read only] 11 lines, 482 characters
>> >
>> >PostScript File Only : PS File Only | PS
>> >HP HP : HP hp | lp -c -s -dhp
>> >HP FP : HP fp | lp -c -s -dfp
>> >HP CP : HP cp | lp -c -s -dcp
>> >QMS860  HP  (INT DSK) : QMS860 HP | lp -s -dqms860
>> >QMS860      (INT DSK) : QMS860 | lpr -s -Pqms860
>> >QMS1700 HP  (RM 302) : QMS1700 HP | lp -s -dqms1700
>> >QMS1700     (RM 302) : QMS1700 | lpr -Pqms1700
>> >HP-4M   HP  (NPPU) : HP-4M NPPU HP | lp -s -dlj4mnppu
>> >HP-4M   HP  (AVN) : HP-4M AVN HP | lp -s -dlj4mavn
>> >PHASER200i  (RM 302) : PHAS200i | lpr -Pph200i
>> >
>> 
>>
>****************************************************************************
><
>> Unidata User Support                                    UCAR Unidata
>> (303)497-8644                                                  P.O. Box
>> address@hidden                                   Boulder, CO
>>
>----------------------------------------------------------------------------
><
>> Unidata WWW Service                        http://www.unidata.ucar.edu/  
>>
>****************************************************************************
><
>