Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Program received signal SIGSEGV, Segmentation fault. #6077

Closed
vicuna opened this issue Jul 16, 2013 · 4 comments
Closed

Program received signal SIGSEGV, Segmentation fault. #6077

vicuna opened this issue Jul 16, 2013 · 4 comments
Assignees

Comments

@vicuna
Copy link

vicuna commented Jul 16, 2013

Original bug ID: 6077
Reporter: berenger
Assigned to: @lefessan
Status: closed (set by @xavierleroy on 2015-12-11T18:21:01Z)
Resolution: duplicate
Priority: normal
Severity: crash
Platform: x86_64
OS: Ubuntu
OS Version: 12.04
Category: ~DO NOT USE (was: OCaml general)
Duplicate of: #5757

Bug description

segfault in invert_pointer_at.

The bug also happens with OCaml 4.00.0 on my system.

Steps to reproduce

opam --version

1.0.1

gdb opam

(gdb) r repository add spoc http://www.algo-prog.info/spoc/distribution/opam
(gdb) r update

Additional information

Starting program: /home/berenger/bin/opam update
Synchronizing ~/.opam/repo/spoc with http://www.algo-prog.info/spoc/distribution/opam.
Synchronizing ~/.opam/repo/default with http://opam.ocamlpro.com.
The following package has been UPDATED upstream:

  • SPOC.130624

Program received signal SIGSEGV, Segmentation fault.
0x000000000061fdd4 in invert_pointer_at ()
(gdb) where
#0 0x000000000061fdd4 in invert_pointer_at ()
#1 0x000000000061ffbb in do_compaction ()
#2 0x0000000000620464 in caml_compact_heap ()
#3 0x00000000006206de in caml_compact_heap_maybe ()
#4 0x0000000000612e4c in caml_major_collection_slice ()
#5 0x0000000000613544 in caml_minor_collection ()
#6 0x00000000006117f3 in caml_garbage_collection ()
#7 0x00000000006216fc in caml_system__code_begin ()
#8 0x00000000005e1d84 in camlParsing__loop_1076 () at parsing.ml:147
#9 0x00000000005e1c75 in camlParsing__loop_1076 () at parsing.ml:145
#10 0x00000000005e24f1 in camlParsing__yyparse_1071 () at parsing.ml:160
#11 0x00000000004fb876 in camlOpamParser__main_1666 ()
#12 0x000000000050397a in camlOpamFile__of_string_2269 ()
#13 0x00000000004fe898 in camlOpamFile__fun_5674 ()
#14 0x0000000000506ba4 in camlOpamFile__with_time_2732 ()
#15 0x00000000004b77b9 in camlOpamState__fun_3210 ()
#16 0x00000000005e3b70 in camlSet__fold_1244 () at set.ml:310
#17 0x00000000005e3b5b in camlSet__fold_1244 () at set.ml:310
#18 0x00000000005e3b5b in camlSet__fold_1244 () at set.ml:310
#19 0x00000000005e3b5b in camlSet__fold_1244 () at set.ml:310
#20 0x00000000005e3b5b in camlSet__fold_1244 () at set.ml:310
#21 0x00000000005e3b5b in camlSet__fold_1244 () at set.ml:310
#22 0x00000000004bcc14 in camlOpamState__load_state_2111 ()
#23 0x00000000004bd133 in camlOpamState__rebuild_state_cache_2174 ()
#24 0x00000000004d0e0b in camlOpamClient__update_aux_1907 ()
#25 0x00000000004edce4 in camlOpamFilename__with_flock_1450 ()
#26 0x00000000004edce4 in camlOpamFilename__with_flock_1450 ()
#27 0x00000000004edce4 in camlOpamFilename__with_flock_1450 ()
#28 0x00000000004edce4 in camlOpamFilename__with_flock_1450 ()
#29 0x00000000004edce4 in camlOpamFilename__with_flock_1450 ()
#30 0x00000000005641c4 in camlCmdliner__eval_term_2170 () at src_ext/cmdliner/src/cmdliner.ml:1142
#31 0x0000000000564672 in camlCmdliner__eval_choice_2211 () at src_ext/cmdliner/src/cmdliner.ml:1178
#32 0x00000000004b71bf in camlOpamMain__entry ()
#33 0x00000000004acf89 in caml_program ()
#34 0x00000000006218da in caml_start_program ()
#35 0x0000000000610355 in caml_main ()
#36 0x0000000000610390 in main ()

@vicuna
Copy link
Author

vicuna commented Jul 16, 2013

Comment author: @lefessan

I think it is a duplicate of #5757, that was fixed after 4.00.0. Have you been able to reproduce the bug with an OCaml version 4.00.1 ?

@vicuna
Copy link
Author

vicuna commented Jul 16, 2013

Comment author: berenger

Yes, the bug also manifests itself with
opam switch 4.01.0dev+trunk

@vicuna
Copy link
Author

vicuna commented Jul 16, 2013

Comment author: berenger

the bug also manifests itself with
4.02.0dev+trunk

@vicuna
Copy link
Author

vicuna commented Jul 16, 2013

Comment author: berenger

The bug is probably the corrected one: I did not recompile my OPAM to test.
I was wrongly assuming OPAM is recompiled upon an opam switch.

Sorry for the false alarm,
F.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants