How to split a data file into separate files with the file names depending upon a column's value?
Hi,
I have a data file xyz.dat similar to the one given below,
I need to split the file into seperate file with the condition that :
1) All the rows which has the same value in column 1 should be in one file.
2) The name of the file should be starting with the column 1's value.
Also the main data file xyz.dat should not be removed.
Hi,
I have a file which contains records of data.
I need to split the file into multiple files depending upon the value of last field.
How do i read the last field of each record in the file???
Regards,
Chaitrali (4 Replies)
Hi All,
I have a file like below:
1016D"ddd","343","1299"
1016D"ddd","3564","1299"
1016D"ddd","3297","1393"
1016D"ddd","32989","1527"
1016D"ddd","346498","1652"
2312D"ddd","3269","1652"
2312D"ddd","328","1652"
2312D"ddd","2224","2100"
3444D"ddd","252","2100"
3444D"ddd","2619","2100"... (4 Replies)
I have a 500 MB XML file from a FileMaker database export, it's formatted horribly (no line breaks at all). The node structure is basically
<FMPXMLRESULT>
<METADATA>
<FIELD att="............." id="..."/>
</METADATA>
<RESULTSET FOUND="1763457">
<ROW att="....." etc="....">
... (16 Replies)
I have a text file with 1,000,000 rows (It is a single column text file of numbers). I would like to separate the text file into 100 files of equal size (i.e. number of rows). The first file will contain the first 10,000 rows, the second row will contain the second 10,000 rows (rows 10,001-20,000)... (2 Replies)
Hi,
As a newbie, I'm desperate ro make my shell script work. I'd like a script which checks all the files in a directory, check the file name, if the file name ends with "extracted", store it in a variable, if it has a suffix of ".roi" stores in another variable. I'm going to use these two... (3 Replies)
hello!
i need a little help from you :) ... i need to split a file into separate files depending on two conditions using scripting. The file has no delimiters. The conditions are col 17 = "P" and col 81 = "*", this will go to one output file; col 17 = "R" and col 81 = " ". Here is an example.
... (3 Replies)
Hi ,
my file look likes below ,
cat file.csv
12/09/2014,50,5,0,300
12/09/2014, ,5,0,300
12/09/2014,50,,,300
i need to split file , the first one contains values (2nd column is 50 , 3rd and fourth column is null )
the second file contains all others
firstfile
... (2 Replies)
Hi,
I have one large files of 100000 rows with header column.
Eg:
Emp Code, Emp Name
101,xxx
102,YYY
103,zzz
...
...
I want to split the files into smaller files with only 30000 rows each..File 1,2 and 3 must have 30000 rows and file 4 must contain 10000 rows.
But the column... (1 Reply)
I am running an ISQL command on Sybase DB and getting output of a query in an CSV file.
The issue is that all the data comes in to the same column, i want them to be separated in different columns.
SQL_COMMAND=command.sql
file=file.txt
formatFile=formatFile.txt
report=report.csv
echo... (1 Reply)
Discussion started by: Sharma331
1 Replies
LEARN ABOUT FREEBSD
gdbserver
gdbserver(1) GNU Development Tools gdbserver(1)NAME
gdbserver - Remote Server for the GNU Debugger
SYNOPSIS
gdbserver
tty prog [args...]
gdbserver tty --attach PID
DESCRIPTION
GDBSERVER is a program that allows you to run GDB on a different machine than the one which is running the program being debugged.
Usage (server (target) side):
First, you need to have a copy of the program you want to debug put onto the target system. The program can be stripped to save space if
needed, as GDBserver doesn't care about symbols. All symbol handling is taken care of by the GDB running on the host system.
To use the server, you log on to the target system, and run the `gdbserver' program. You must tell it (a) how to communicate with GDB, (b)
the name of your program, and (c) its arguments. The general syntax is:
target> gdbserver COMM PROGRAM [ARGS ...]
For example, using a serial port, you might say:
target> gdbserver /dev/com1 emacs foo.txt
This tells gdbserver to debug emacs with an argument of foo.txt, and to communicate with GDB via /dev/com1. Gdbserver now waits patiently
for the host GDB to communicate with it.
To use a TCP connection, you could say:
target> gdbserver host:2345 emacs foo.txt
This says pretty much the same thing as the last example, except that we are going to communicate with the host GDB via TCP. The
`host:2345' argument means that we are expecting to see a TCP connection from `host' to local TCP port 2345. (Currently, the `host' part
is ignored.) You can choose any number you want for the port number as long as it does not conflict with any existing TCP ports on the
target system. This same port number must be used in the host GDBs `target remote' command, which will be described shortly. Note that if
you chose a port number that conflicts with another service, gdbserver will print an error message and exit.
On some targets, gdbserver can also attach to running programs. This is accomplished via the --attach argument. The syntax is:
target> gdbserver COMM --attach PID
PID is the process ID of a currently running process. It isn't necessary to point gdbserver at a binary for the running process.
Usage (host side):
You need an unstripped copy of the target program on your host system, since GDB needs to examine it's symbol tables and such. Start up
GDB as you normally would, with the target program as the first argument. (You may need to use the --baud option if the serial line is
running at anything except 9600 baud.) Ie: `gdb TARGET-PROG', or `gdb --baud BAUD TARGET-PROG'. After that, the only new command you need
to know about is `target remote'. It's argument is either a device name (usually a serial device, like `/dev/ttyb'), or a HOST:PORT
descriptor. For example:
(gdb) target remote /dev/ttyb
communicates with the server via serial line /dev/ttyb, and:
(gdb) target remote the-target:2345
communicates via a TCP connection to port 2345 on host `the-target', where you previously started up gdbserver with the same port number.
Note that for TCP connections, you must start up gdbserver prior to using the `target remote' command, otherwise you may get an error that
looks something like `Connection refused'.
OPTIONS
You have to supply the name of the program to debug and the tty to communicate on; the remote GDB will do everything else. Any remaining
arguments will be passed to the program verbatim.
SEE ALSO
`gdb' entry in info; Using GDB: A Guide to the GNU Source-Level Debugger, Richard M. Stallman and Roland H. Pesch, July 1991.
COPYING
Copyright (c) 1993 Free Software Foundation, Inc.
Permission is granted to make and distribute verbatim copies of this manual provided the copyright notice and this permission notice are
preserved on all copies.
Permission is granted to copy and distribute modified versions of this manual under the conditions for verbatim copying, provided that the
entire resulting derived work is distributed under the terms of a permission notice identical to this one.
Permission is granted to copy and distribute translations of this manual into another language, under the above conditions for modified
versions, except that this permission notice may be included in translations approved by the Free Software Foundation instead of in the
original English.
Cygnus Support 2 November 1993 gdbserver(1)