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

non-deterministic segmentation fault #7964

Closed
vicuna opened this issue Nov 30, 2002 · 3 comments
Closed

non-deterministic segmentation fault #7964

vicuna opened this issue Nov 30, 2002 · 3 comments
Labels
bug

Comments

@vicuna
Copy link

vicuna commented Nov 30, 2002

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

Bug description

Full_Name: Andy Chou
Version: 3.06
OS: Linux
Submission from: 216.100.136.162 (216.100.136.162)

I have a long-running process that occassionally dies with a seg fault. It's
not reproducible consistently, but it always happens when the process is run
long enough. It dumps core. I can send a binary and a core dump, if that would
help. Here's the backtrace the core file gives in gdb:

#0 chunk_free (ar_ptr=0xb2, p=0x2c393030) at malloc.c:3049
#1 0x2ab41f9a in __libc_free (mem=0x2c393038) at malloc.c:3023
#2 0x809389c in re_free ()
#3 0x808de33 in free_regexp ()
#4 0x8094bc9 in sweep_slice ()
#5 0x8094e16 in major_collection_slice ()
#6 0x8095451 in minor_collection ()
#7 0x80954a7 in check_urgent_gc ()
#8 0x809e1e0 in alloc_custom ()
#9 0x808de5d in alloc_regexp ()
#10 0x808dea5 in str_compile_regexp ()
#11 0x8072a9d in Str__regexp_91 ()
#12 0x2d714e8c in ?? ()
#13 0x2d714e8c in ?? ()
#14 0x2d7118d4 in ?? ()
Cannot access memory at address 0x1

I have not tried the bytecode compiler, but I plan to soon.

-Andy
@vicuna
Copy link
Author

vicuna commented Dec 1, 2002

Comment author: administrator

I have a long-running process that occassionally dies with a seg fault. It's
not reproducible consistently, but it always happens when the process is run
long enough.

Does this program use signals ? Do you run it on MIPS, Alpha, or PowerPC ?
We have a known bug with signals on these architectures in 3.06 (and all
previous version). The bug doesn't affect the bytecode.

It does use signals, but it's on i386 Linux. I've temporarily resolved
the problem by changing the implementation to not create regexp's all over
the place. Instead, I just create the regexp's I need at the beginning of
the program and reuse them. This way they never need to be freed.

-Andy

@vicuna
Copy link
Author

vicuna commented Dec 1, 2002

Comment author: administrator

Hello Andy,

I have a long-running process that occassionally dies with a seg fault. It's
not reproducible consistently, but it always happens when the process is run
long enough.

Does this program use signals ? Do you run it on MIPS, Alpha, or PowerPC ?
We have a known bug with signals on these architectures in 3.06 (and all
previous version). The bug doesn't affect the bytecode.

-- Damien

@vicuna
Copy link
Author

vicuna commented Jan 7, 2003

Comment author: administrator

Could not reproduce.

@vicuna vicuna closed this as completed Jan 7, 2003
@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