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.

Sign up for GitHub

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

comment for README.md #2

Closed
matthewlinks opened this issue May 19, 2022 · 1 comment
Closed

comment for README.md #2

matthewlinks opened this issue May 19, 2022 · 1 comment

Comments

@matthewlinks
Copy link

Under Developer Quickstart you may want to change the URL to https://github.com/nanoporetech/dorado.git

cheers,

Matt
@vellamike
Copy link
Collaborator

Well spotted :) thanks!

@vdejager vdejager mentioned this issue May 24, 2022
Closed
@vdejager vdejager mentioned this issue Oct 17, 2022
Closed
@olawa olawa mentioned this issue Dec 9, 2022
Closed
@Kirk3gaard Kirk3gaard mentioned this issue Jan 9, 2023
Closed
@jagos01 jagos01 mentioned this issue Feb 16, 2023
Closed
@aCoalBall aCoalBall mentioned this issue May 16, 2023
Closed
@MarkiyanSV MarkiyanSV mentioned this issue May 22, 2023
Closed
@Kirk3gaard Kirk3gaard mentioned this issue May 23, 2023
Closed
@AyshaSezmis AyshaSezmis mentioned this issue May 24, 2023
Closed
@krpcem krpcem mentioned this issue Jun 20, 2023
Closed
@shiying-sxu shiying-sxu mentioned this issue Jul 16, 2023
Closed
@dbernick dbernick mentioned this issue Jul 31, 2023
Open
@ymcki ymcki mentioned this issue Aug 8, 2023
Closed
@Kirk3gaard Kirk3gaard mentioned this issue Aug 9, 2023
Closed
tijyojwad pushed a commit that referenced this issue Nov 14, 2023
@blawrence-ont
[INSTX-2496] Fix a crash with GCC8 seen on CI
0c9cd2a 
The following crash was seen on CI when compiling with GCC 8.4.0 and
with ASAN enabled:
  ==11805==ERROR: AddressSanitizer: SEGV on unknown address 0x001200000000 (pc 0xffff68c2296c bp 0xffffc1c19400 sp 0xffffc1c19400 T0)
  ==11805==The signal is caused by a WRITE memory access.
    #0 0xffff68c2296b  (/lib/aarch64-linux-gnu/libc.so.6+0x8396b)
    #1 0xffff876bedc3  (/usr/lib/aarch64-linux-gnu/libasan.so.5+0x36dc3)
    #2 0xaaaad510039b in _GLOBAL__sub_I_00099_1__ZN6dorado8splitter7subreadERKNS_11SimplexReadESt8optionalISt4pairImmEES6_ (dorado_tests+0x17639b)
    #3 0xaaaad5c9ea1f in __libc_csu_init (dorado_tests+0xd14a1f)

The static initialiser that calls into libasan is one of ASANs inserted
init functions (__asan_init, __asan_version_mismatch_check_v8, or
__asan_register_globals) though gdb refuses to ptrace so I can't tell
which. None of them should crash so this feels like a compiler bug,
though I'm unable to determine exactly what's triggering it since a
disassembly of the static initialiser doesn't change between the broken
and "fixed" versions of the code (plt addresses notwithstanding).
@ritma001 ritma001 mentioned this issue Dec 4, 2023
Closed
@tnn111 tnn111 mentioned this issue Dec 11, 2023
Closed
@DCossey DCossey mentioned this issue Dec 19, 2023
Open
@krobik26 krobik26 mentioned this issue Jan 19, 2024
Closed
@AzlanNI AzlanNI mentioned this issue Jan 22, 2024
Closed
@fayora fayora mentioned this issue Jan 23, 2024
Closed
@ericmsmall ericmsmall mentioned this issue Feb 7, 2024
Open
@peterthorpe5 peterthorpe5 mentioned this issue Feb 8, 2024
Closed
@pbpearman pbpearman mentioned this issue Apr 21, 2024
Closed
@faulk-lab faulk-lab mentioned this issue May 22, 2024
Closed
@pre-mRNA pre-mRNA mentioned this issue May 25, 2024
Open
@VBHerrenC VBHerrenC mentioned this issue May 28, 2024
Closed
@markme123 markme123 mentioned this issue Jun 1, 2024
Closed
@fehofman fehofman mentioned this issue Jun 4, 2024
Open
@NStrowbridge NStrowbridge mentioned this issue Jun 5, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@vellamike @matthewlinks