Hide Forgot
Description of problem: If you run: procinfo -a A segfault will occur. A stack trace of the core file looks like: (gdb) bt #0 0x4207a6db in strlen () from /lib/tls/libc.so.6 #1 0x420477ed in vfprintf () from /lib/tls/libc.so.6 #2 0x4204f3e2 in printf () from /lib/tls/libc.so.6 #3 0x0804c683 in strcpy () #4 0x0804d20a in strcpy () #5 0x420156a4 in __libc_start_main () from /lib/tls/libc.so.6 Version-Release number of selected component (if applicable): 18-8 How reproducible: Always Steps to Reproduce: 1. Run: procinfo -a Actual results: A segfault occurs. Expected results: Not that (-; Additional info:
This problem isn't reproduceable on any machines I have available, which implies that it only happens with the specific contents of the /proc files on your system, or something in them is triggering this. In order to fix it however, we'll need you to narrow down the problem. Can you install the -debuginfo packages for procinfo after rebuilding it and then run it in gdb to find where the exact failure is?
I can't really proceed with this bug report unless I can personally reproduce the problem, or receive more information from you. I have tried to reproduce this on numerous systems to no avail. There are other currently open procinfo bugs of which yours might be a duplicate, however I can't conclude that without further feedback from you on this problem. Please examine bug #89176, bug #112533 to see if either of them are the same problem you are encountering, which in both cases seems to be due to procinfo assuming the wrong maximum number of character devices available. How many char devices does your system have present when this problem occurs? Please respond ASAP, so I can clear out these issues and update procinfo.
Closing bug as 'WORKSFORME' state, as I'm unable to reproduce this problem locally.