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

Jump to bottom

AMD Opteron: crash in caml_oldify_mopup #8449

Closed
vicuna opened this issue Jan 19, 2004 · 2 comments
Closed

AMD Opteron: crash in caml_oldify_mopup #8449

vicuna opened this issue Jan 19, 2004 · 2 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented Jan 19, 2004

Original bug ID: 2047
Reporter: administrator
Status: closed
Resolution: not a bug
Priority: normal
Severity: minor
Category: ~DO NOT USE (was: OCaml general)

Bug description

Full_Name: Aleksey Nogin
Version: CVS from Jan 17, 2004
OS: Fedora Core Development (AKA RawHide).
Submission from: charter-242-037.caltech.edu (131.215.242.37)

I just got a reproducible crash in caml_oldify_mopup:

(gdb) bt
#0 0x0000000000ac5757 in caml_oldify_mopup ()
#1 0x0000000000ac5858 in caml_empty_minor_heap ()
#2 0x0000000000ac591a in caml_minor_collection ()
#3 0x0000000000ac42ad in caml_garbage_collection ()
#4 0x0000000000ad0d89 in caml_call_gc ()
#5 0x4157782bc0000000 in ?? ()
#6 0x3f97af99f4893e68 in ?? ()

Not sure what can be done to debug it further.
@vicuna
Copy link
Author

vicuna commented Jan 19, 2004

Comment author: administrator

On Monday, January 19, 2004, at 04:10 AM, nogin@cs.caltech.edu wrote:

Full_Name: Aleksey Nogin
Version: CVS from Jan 17, 2004
OS: Fedora Core Development (AKA RawHide).
Submission from: charter-242-037.caltech.edu (131.215.242.37)

I just got a reproducible crash in caml_oldify_mopup:

As usual when there is a crash in the GC, this is most likely
due to a pointer garbled by some other piece of code. The prime
suspect is of course the C code you linked in your program, if
any.

Not sure what can be done to debug it further.

Painstakingly trace back the pointer in question through the
execution of the program to find where and why is was overwritten.

If your program doesn't use any C code, or if you are sure the
C code is correct, then we are interested in the source code
for your reproducible test case.

-- Damien

@vicuna
Copy link
Author

vicuna commented Jun 19, 2004

Comment author: administrator

No repro case. Bug closed 2004-06-19, XL.

@vicuna vicuna closed this as completed Jun 19, 2004
@vicuna vicuna added the bug label Mar 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@vicuna