Bug#653178: "/bin/cat whatever just segfaults" (Re: Bug#653178: reopen)
tag 653178 + moreinfo
tag 653178 + unreproducible
Le 03/01/2012 08:13, Eric Valette a écrit :
> On 03/01/2012 04:25, Jonathan Nieder wrote:
>> Hi Eric,
>> Eric Valette wrote:
>>> reopen #653179
>> Rather than fiddling with metadata, why not provide some information
>> to help others reproduce or otherwise understand your report? /bin/cat
>> works fine for me.  has some hints.
>> Sorry for the trouble,
>>  http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
> cat whatever segfaults is simple enough to reproduce. Except it
> segfaults not each time but 8 out of 10 times.
> And again its a libc error. Downgrading from -23 to -21 fixed the
> problem. When I boot, hostname it null as init script hostname.sh does
> On arm and on a NAS without console (dlink323) this kind of libc problem
> may brick the device...
It's not reproducible here (I tried on 3 different armel machines), so
it looks like this problem is local to your computer. Also nothing
significant changed between -21 and -23, at least from the changelog.
Unfortunately without more details, we'll have to ignore this bug.
Please provide us some more details so that the issue can be debugged:
- Does only cat segfault or does other programs also segfault?
- Does it segfaults with every file or only with some specific files?
- Is there any useful message other than "Segmentation fault"? Does it
at least start to print things? The best would be for you to copy and
paste the output of the command.
- Any useful information in dmesg?
- What is the output of 'which cat'? of 'ldd /bin/cat'?
- Could you please try to run it with gdb or with strace and send us the
PS: Please be polite with bug reports and provide useful informations,
things like 'uploading a totally untested package' (which is clearly)
wrong just make me feeling like totally ignoring this bug report. Also
please avoid sending multiple empty mails with sparse data in the subject.
Aurelien Jarno GPG: 1024D/F1BCDB73