Cannot index / search one file
- Lingua principale
- Go
- Stelle
- 4k
- Fork
- 403
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Descrizione
```
What steps will reproduce the problem?
1. Index the attached file with cindex
2. Search for a pattern inside it
3. No hits
What is the expected output? What do you see instead?
repro$
repro$ cindex -reset
repro$ cindex badfile
2013/03/13 18:51:52 index /tmp/repro/badfile
2013/03/13 18:51:52 flush index
2013/03/13 18:51:52 merge 0 files + mem
2013/03/13 18:51:52 0 data bytes, 92 index bytes
2013/03/13 18:51:52 done
repro$ cindex -list
/tmp/repro/badfile
repro$
repro$
repro$
repro$ grep main badfile
libc.so.6 __libc_start_main
torch main
torch realmain(int, char**)
libglib-2.0.... g_main_context_iteration
libglib-2.0.... g_main_context_prepare
libglib-2.0.... g_main_context_dispatch
#85 0x00000032f5c38f0e in g_main_context_dispatch () from
/lib64/libglib-2.0.so.0
#87 0x00000032f5c3ca3a in g_main_context_iteration () from
/lib64/libglib-2.0.so.0
#93 0x000000000040e74d in realmain(int, char**) ()
#94 0x000000000040e933 in main ()
repro$
repro$ csearch main <= no results here !!
repro$
repro$ grep threads badfile
============ All threads ==========
============ All threads ==========
repro$
repro$ csearch threads <= no results here !!
repro$
I cannot find (with csearch) text that is in a file I have indexed (cindex)
What version of the product are you using? On what operating system?
I'm using the Linux binaries that are available on the Download page.
I tried to compile go / codesearch but couldn't make it work (my go
install might be funky).
Please provide any additional information below.
It looks like the problem happens at indexing time.
```
Original issue reported on code.google.com by `bserg...@gmail.com` on 14 Mar 2013 at 1:57
Attachments:
- [badfile](https://storage.googleapis.com/google-code-attachments/codesearch/issue-30/comment-0/badfile)
Guida per i contributori
Apri la guida per i contributori
Direzione di ricerca
Riproduci il report con il badfile allegato usando cindex -reset, cindex badfile e csearch per main e threads. Inizia tracciando i punti di ingresso di cindex e csearch e il modo in cui questo file viene gestito durante l’indicizzazione; il lavoro è completato quando csearch restituisce il testo visibile in badfile.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Valutazione
- Stack tecnologico
- go
- Ambito
- cli, search
- Tipo di issue
- Bug
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Stato di attività
- Ferma
- Chiarezza
- Da chiarire
- Idoneità per principianti
- 35/100