#9372 closed bug (duplicate)
grep with -i-Param is crashing
| Reported by: | jahaiku | Owned by: | nobody |
|---|---|---|---|
| Priority: | normal | Milestone: | R1 |
| Component: | - General | Version: | R1/alpha4.1 |
| Keywords: | Cc: | ||
| Blocked By: | #9342 | Blocking: | |
| Platform: | x86 |
Description
If you execute grep on a recent build like this
grep -r -i ToSearch .
it is crashing with the attached Backtrace. If you do not call grep with -i all is OK.
Attachments (1)
Change History (7)
by , 12 years ago
| Attachment: | grep-231-debug-12-01-2013-19-07-31.report added |
|---|
comment:1 by , 12 years ago
| Blocked By: | 9342 added |
|---|---|
| Resolution: | → duplicate |
| Status: | new → closed |
comment:2 by , 12 years ago
What hrev of Haiku did you see this on? What version of grep (grep --version)?
gcc2, gcc2h, gcc4, gcc4h, x86_64?
follow-up: 4 comment:3 by , 12 years ago
This was a gcc4 build of hrev45150. The grep version is the included version of this hrev. This is the packagename: grep-2.14-x86-gcc4-2012-12-28.zip
BTW: Is it possible to include the gcc info and the hrev into the automatically generated bug report?
follow-up: 5 comment:4 by , 12 years ago
Replying to jahaiku:
BTW: Is it possible to include the gcc info and the hrev into the automatically generated bug report?
The hrev is already in there. Discovering the compiler(s) used would be a bit less trivial though and not something I'd have time to look at any time soon.
follow-up: 6 comment:5 by , 12 years ago
Replying to anevilyak:
Replying to jahaiku:
BTW: Is it possible to include the gcc info and the hrev into the automatically generated bug report?
The hrev is already in there. Discovering the compiler(s) used would be a bit less trivial though and not something I'd have time to look at any time soon.
In the AboutSystem there is a info saying, gcc4 or gcc2, isn't this the needed info?
comment:6 by , 12 years ago
Replying to jahaiku:
In the AboutSystem there is a info saying, gcc4 or gcc2, isn't this the needed info?
AboutSystem has this hardcoded at compile time. The debugger cannot rely on that since it will eventually also support remote debugging, in which case it has to be queried from the target system, so discovering it is a bit more involved there.
Backtrace of the crash