Login
[x]
Log in using an account from:
Fedora Account System
Red Hat Associate
Red Hat Customer
Or login using a Red Hat Bugzilla account
Forgot Password
Login:
Hide Forgot
Create an Account
Red Hat Bugzilla – Attachment 832282 Details for
Bug 1037789
Midori segfaults when using default search engine
[?]
New
Simple Search
Advanced Search
My Links
Browse
Requests
Reports
Current State
Search
Tabular reports
Graphical reports
Duplicates
Other Reports
User Changes
Plotly Reports
Bug Status
Bug Severity
Non-Defaults
|
Product Dashboard
Help
Page Help!
Bug Writing Guidelines
What's new
Browser Support Policy
5.0.4.rh83 Release notes
FAQ
Guides index
User guide
Web Services
Contact
Legal
This site requires JavaScript to be enabled to function correctly, please enable it.
Midori gdb
midori-gdb.txt (text/plain), 2.51 KB, created by
Paul Whalen
on 2013-12-03 19:58:27 UTC
(
hide
)
Description:
Midori gdb
Filename:
MIME Type:
Creator:
Paul Whalen
Created:
2013-12-03 19:58:27 UTC
Size:
2.51 KB
patch
obsolete
>[pwhalen@localhost ~]$ gdb midori >GNU gdb (GDB) Fedora 7.6.50.20130731-16.fc20 >Copyright (C) 2013 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 "armv7hl-redhat-linux-gnueabi". >Type "show configuration" for configuration details. >For bug reporting instructions, please see: ><http://www.gnu.org/software/gdb/bugs/>. >Find the GDB manual and other documentation resources online at: ><http://www.gnu.org/software/gdb/documentation/>. >For help, type "help". >Type "apropos word" to search for commands related to "word". >.. >Reading symbols from /usr/bin/midori...Reading symbols from /usr/lib/debug/usr/bin/midori.debug...done. >done. >(gdb) run >Starting program: /usr/bin/midori >[Thread debugging using libthread_db enabled] >Using host libthread_db library "/lib/libthread_db.so.1". >[New Thread 0xb1d99250 (LWP 2013)] >[New Thread 0xb11ff250 (LWP 2014)] >[New Thread 0xb08fd250 (LWP 2015)] >[Thread 0xb08fd250 (LWP 2015) exited] >[New Thread 0xb08fd250 (LWP 2016)] >[New Thread 0xafeff250 (LWP 2017)] >[Thread 0xafeff250 (LWP 2017) exited] >[New Thread 0xafeff250 (LWP 2018)] >[New Thread 0xaf0ff250 (LWP 2019)] >[New Thread 0xae8ff250 (LWP 2020)] >[New Thread 0xae0ff250 (LWP 2021)] >[Thread 0xaf0ff250 (LWP 2019) exited] >[New Thread 0xaf0ff250 (LWP 2022)] >[New Thread 0xa893e250 (LWP 2023)] >[New Thread 0xa813e250 (LWP 2024)] >[New Thread 0xa793e250 (LWP 2025)] >[New Thread 0xa713e250 (LWP 2026)] >[New Thread 0xa693e250 (LWP 2027)] >[New Thread 0xa613e250 (LWP 2028)] >[New Thread 0xa593e250 (LWP 2029)] >[New Thread 0xa513e250 (LWP 2030)] >[New Thread 0xa493e250 (LWP 2031)] >[Thread 0xa493e250 (LWP 2031) exited] >[Thread 0xa613e250 (LWP 2028) exited] >[Thread 0xa593e250 (LWP 2029) exited] >[Thread 0xa893e250 (LWP 2023) exited] >[Thread 0xa793e250 (LWP 2025) exited] >[Thread 0xa513e250 (LWP 2030) exited] >[Thread 0xae8ff250 (LWP 2020) exited] >[Thread 0xa693e250 (LWP 2027) exited] >[Thread 0xa713e250 (LWP 2026) exited] >[New Thread 0xa693e250 (LWP 2032)] >[New Thread 0xa713e250 (LWP 2033)] >[New Thread 0xae8ff250 (LWP 2034)] >[Thread 0xa693e250 (LWP 2032) exited] >[Thread 0xa713e250 (LWP 2033) exited] >[Thread 0xae8ff250 (LWP 2034) exited] >[New Thread 0xae8ff250 (LWP 2035)] >[New Thread 0xa713e250 (LWP 2036)] > >Program received signal SIGSEGV, Segmentation fault. >0xa81b562c in ?? (Cannot access memory at address 0x1 >) >(gdb) >
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1037789
:
832281
|
832282
|
832285
|
833251