- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I need to debug a program that relies on piped input, i.e.
pipe.in | foo
where foo is created with ifort. I've tried everything I can think of (which isn't much) based on the idb manual, such as:
[roberts628@AEDE320RH code]$ cat pipe.in | ./agrisk &
[1] 17088
[roberts628@AEDE320RH code]$ jobs
[1]+ Done cat pipe.in | ./agrisk
[roberts628@AEDE320RH code]$ idb -pid 17088 agrisk
Linux Application Debugger for 32-bit applications, Version 7.3.2, Build 20031209
------------------
object file name: agrisk
Error: could not attach to the debuggee
Could not attach to process 17088.
No image loaded ... Recovering ...
(idb)
Ideally, I'd like to get it to run in DDD, but I figure that if I can't even get it to run in the shell, then DDD can wait.
I'm sorry that this is more of a linux question than ifort, but thanks for any thoughts/suggestions.
Matt.
pipe.in | foo
where foo is created with ifort. I've tried everything I can think of (which isn't much) based on the idb manual, such as:
[roberts628@AEDE320RH code]$ cat pipe.in | ./agrisk &
[1] 17088
[roberts628@AEDE320RH code]$ jobs
[1]+ Done cat pipe.in | ./agrisk
[roberts628@AEDE320RH code]$ idb -pid 17088 agrisk
Linux Application Debugger for 32-bit applications, Version 7.3.2, Build 20031209
------------------
object file name: agrisk
Error: could not attach to the debuggee
Could not attach to process 17088.
No image loaded ... Recovering ...
(idb)
Ideally, I'd like to get it to run in DDD, but I figure that if I can't even get it to run in the shell, then DDD can wait.
I'm sorry that this is more of a linux question than ifort, but thanks for any thoughts/suggestions.
Matt.
Link Copied
0 Replies

Reply
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page