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

Not work in Fedora 17 #15

Closed
Vascom opened this issue May 7, 2012 · 8 comments
Closed

Not work in Fedora 17 #15

Vascom opened this issue May 7, 2012 · 8 comments
Assignees
Labels

Comments

@Vascom
Copy link

Vascom commented May 7, 2012

I am successfully compiled grive in Fedora 17 x86_64. But at startup it has Segmentation fault and not work.

@nestal
Copy link
Member

nestal commented May 7, 2012

I am using Fedora 16 and it works fine. Do you have a gdb backtrace?

Also are you using master or v0.0.4?

@Vascom
Copy link
Author

Vascom commented May 7, 2012

I am use master.
commit 9b574b5

How can I get gdb backtrace?

@ghost ghost assigned nestal May 7, 2012
@nestal
Copy link
Member

nestal commented May 7, 2012

first, load gdb with "gdb grive"
in the gdb prompt, type "run"
when it gets a seg fault, it will stop at the code that triggers the seg fault.
type "bt" to get a backtrace and post it here.

@Vascom
Copy link
Author

Vascom commented May 7, 2012

$ gdb grive
GNU gdb (GDB) Fedora (7.4.50.20120120-42.fc17)
Copyright (C) 2012 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later http://gnu.org/licenses/gpl.html
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
http://www.gnu.org/software/gdb/bugs/...
Reading symbols from /home/vascom/match065-grive-9b574b5/grive/grive...(no debugging symbols found)...done.
(gdb) run -a
Starting program: /home/vascom/match065-grive-9b574b5/grive/grive -a
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib64/libthread_db.so.1".

Program received signal SIGSEGV, Segmentation fault.
0x0000003503e3388b in ?? () from /lib64/libcurl.so.4
Missing separate debuginfos, use: debuginfo-install cyrus-sasl-lib-2.1.23-29.fc17.x86_64 expat-2.1.0-1.fc17.x86_64 glibc-2.15-35.fc17.x86_64 json-c-0.9-4.fc17.x86_64 keyutils-libs-1.5.5-2.fc17.x86_64 krb5-libs-1.10-6.fc17.x86_64 libcom_err-1.42-4.fc17.x86_64 libcurl-7.24.0-2.fc17.x86_64 libgcc-4.7.0-4.fc17.x86_64 libidn-1.24-1.fc17.x86_64 libselinux-2.1.10-3.fc17.x86_64 libssh2-1.4.1-2.fc17.x86_64 libstdc++-4.7.0-4.fc17.x86_64 nspr-4.9-2.fc17.x86_64 nss-3.13.4-3.fc17.x86_64 nss-softokn-freebl-3.13.4-2.fc17.x86_64 nss-util-3.13.4-2.fc17.x86_64 openldap-2.4.31-1.fc17.x86_64 openssl-1.0.0i-1.fc17.x86_64 zlib-1.2.5-6.fc17.x86_64
(gdb) bt
#0 0x0000003503e3388b in ?? () from /lib64/libcurl.so.4
#1 0x0000003503e0f70a in ?? () from /lib64/libcurl.so.4
#2 0x0000003503e1da02 in ?? () from /lib64/libcurl.so.4
#3 0x00007ffff7ddfd5f in gr::http::Agent::Escape(std::string const&) ()
from /home/vascom/match065-grive-9b574b5/libgrive/libgrive.so.0
#4 0x00007ffff7de0b16 in gr::OAuth2::MakeAuthURL(std::string const&, std::string const&) () from /home/vascom/match065-grive-9b574b5/libgrive/libgrive.so.0
#5 0x00000000004034d8 in main ()

@nestal
Copy link
Member

nestal commented May 8, 2012

This is a double free problem. It got fixed by later commits

@match065
Copy link
Member

match065 commented May 8, 2012

I just push the fix. Can you please test again?

@Vascom
Copy link
Author

Vascom commented May 8, 2012

OK. Now it work. But it download files in directory where I run grive, not in ~/.grive

@nestal
Copy link
Member

nestal commented May 9, 2012

That is expected.

@Vascom Vascom closed this as completed May 9, 2012
@ghost ghost mentioned this issue Dec 2, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants