- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- sed 's/\\//g' < /tmp/wtg1 gives Memory fault(cored...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 02:34 AM
05-15-2002 02:34 AM
sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
Any other char is OK - sed 's/\|//g' or sed 's/4//g' or chars enclosing the "\" chars - sed 's/4*05775//g'.
Also get a core dump on occasion searching file for "\" char in more. Try to vi the file but get the line too long message. od -c doesn't show any dodgy chars.
Created a dummy file with "\" chars and sed can find the "\" file and remove or replace them.
Anyone with any ideas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 02:41 AM
05-15-2002 02:41 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
http://hpux.cs.utah.edu/hppd/hpux/Gnu/sed-3.02/
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 02:41 AM
05-15-2002 02:41 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
Would it be possible for you to attach a couple of lines of the file as an example? Is it possible that the \ is showing as part of a newline character, \n or a tab \t ?
John
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 02:50 AM
05-15-2002 02:50 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
why don't you simply use "tr" for that:
tr -d "\\" < input.file > output.file
this would delete all backslashes from the input.file - without any problem about line-lenght limits...
Just my $0.02,
Wodisch
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 03:07 AM
05-15-2002 03:07 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
The previous 2 lines are OK wc output is 2 247 5306 /tmp/wtg2 so it doesn't seem to be a size limit.
od -c output of the lines with \ in below, dunno if it'll be readable though
0004640 | 1 | p r z e l - 1 1 1 0 0 0 4
0004660 5 2 8 5 4 \ 0 1 \ 0 5 7 7 5
0004700 |
0004720 3 3 8 1 5 | 0 |
0004740 0 | 0 | 0 | 0 |
0004760 | 1 | 5 1 2 6
0005000 | 1 | 0 | 0 | 5 2 4 0 3 0
0005020 3 3 7 5 | R 0 1 1 5 6
0005040 6 0 1 0 | 1 0 1 0 1 0
0005060 2 3 | 2 6 - 1 3 9 - | | N | 0
0005100 0 2 7 3 9 6 2 0 4 5 5 | 1 1 4 0
0005120 1 0 1 0 0 0 2 7 3 9 6 2 0 4 5 5
0005140 2 5 2 1 0 0 | 6 8 \n
0005152
wodisch tried your suggestion, no core dump but it didn't find the "\" char. No change to output.
Thanks for your interest.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 03:15 AM
05-15-2002 03:15 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
# perl -pe 'tr/\\//d' infile >outfile
if you want to translate octals, you could use
# perl -pe 's/\\([0-7]+)/oct$1/ge' infile >outfile
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 04:12 AM
05-15-2002 04:12 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
Symptoms:
PHCO_22760:
1. sed(1) dumps core when the length of input string is
larger than 2K bytes.
once loaded it fixed the problem though dont quite see the logic here when it worked ok for a larger line. Ran other tests with files I created over 2666 chars long on other system built from same ignite tape and sed doesn't produce a core dump. Beats me so I'll just load the path on 'em all.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
05-15-2002 04:15 AM
05-15-2002 04:15 AM
Re: sed 's/\\//g' < /tmp/wtg1 gives Memory fault(coredump)
Symptoms:
PHCO_22760:
1. sed(1) dumps core when the length of input string is
larger than 2K bytes.
once loaded it fixed the problem though dont quite see the logic here when it worked ok for a larger line. Ran other tests with files I created over 2666 chars long on other system built from same ignite tape and sed doesn't produce a core dump. Beats me so I'll just load the path on 'em all.
The perl command worked OK aswell. Thanks