How can I break at the very start of a program on OS X (10.6) without debug symbols?
I'm debugging an issue where my machine hangs and can't do certain things (at least anything involving networking). The programs I can use to try to identify the hang also hang on launch, so I'd like to start a program but not actually run it until the hang occurs, in the hopes that either the program runs or the place it hangs helps me to diagnose the issue.
I tried just setting breakpoints at the addresses that show up in the backtrace, but execution didn't stop.
Breakpoint 2, 0x000000010005cc78 in write$NOCANCEL ()
(gdb) bt
#0 0x000000010005cc78 in write$NOCANCEL ()
#1 0x000000010005cc74 in __swrite ()
#2 0x000000010005cbfd in _swrite ()
#3 0x000000010005cb42 in __sflush ()
#4 0x0000000100061361 in __swbuf ()
#5 0x0000000100093474 in putchar ()
#6 0x0000000100003ce7 in ?? ()
#7 0x000000010000090c in ?? ()
(gdb) b *0x000000010000090c
Breakpoint 3 at 0x10000090c
(gdb) b *0x0000000100003ce7
Breakpoint 4 at 0x100003ce7
(gdb) run
The program being debugged has been started already.
Start it from the beginning? (y or n) y
Starting program: [...]
Breakpoint 2, 0x000000010005cc78 in write$NOCANCEL ()
(gdb) bt
#0 0x000000010005cc78 in write$NOCANCEL ()
#1 0x000000010005cc74 in __swrite ()
#2 0x000000010005cbfd in _swrite ()
#3 0x000000010005cb42 in __sflush ()
#4 0x0000000100061361 in __swbuf ()
#5 0x0000000100093474 in putchar ()
#6 0x0000000100003ce7 in ?? ()
#7 0x000000010000090c in ?? ()
b __dyld__dyld_start works. (Thanks to #kongtomorrow.)
Related
I installed the pearl theme 2.3x after installed and did the configuration after that I got this error I can't understand the issue please help me to fix this issue.
I using Cloudflare server and the os is Debian gnu Linux 9 and Magento version is 2.3
Issue
1 exception(s): Exception #0
(Magento\Framework\Config\Dom\ValidationException): Element 'font':
This element is not expected. Expected is one of ( title, css, link,
meta, script, remove, attribute ). Line: 1285
Element 'font': This element is not expected. Expected is one of (
title, css, link, meta, script, remove, attribute ). Line: 1293
Exception #0 (Magento\Framework\Config\Dom\ValidationException):
Element 'font': This element is not expected. Expected is one of (
title, css, link, meta, script, remove, attribute ). Line: 1285
Element 'font': This element is not expected. Expected is one of (
title, css, link, meta, script, remove, attribute ). Line: 1293
#1 Magento\Framework\Config\Dom->__construct('createObject('Magento\Framewor...',
array('create('Magento\Framewor...',
array('xml' => '
'/mnt/data/home/2...', 'validationState' =>
&Magento\Framework\App\Arguments\ValidationState#000000003e5a6782000000001b0cec1a#))
called at
[vendor/magento/framework/ObjectManager/ObjectManager.php:56]
#4 Magento\Framework\ObjectManager\ObjectManager->create('Magento\Framewor...',
array('xml' => '
'/mnt/data/home/2...', 'validationState' =>
&Magento\Framework\App\Arguments\ValidationState#000000003e5a6782000000001b0cec1a#))
called at [vendor/magento/framework/Config/DomFactory.php:43]
#5 Magento\Framework\Config\DomFactory->createDom(array('xml' => ' '/mnt/data/home/2...',
'validationState' =>
&Magento\Framework\App\Arguments\ValidationState#000000003e5a6782000000001b0cec1a#))
called at
[vendor/magento/framework/View/Model/Layout/Update/Validator.php:141]
#6 Magento\Framework\View\Model\Layout\Update\Validator->isValid('_validateMergedLayout('LAYOUT_frontend_...',
'\n load() called at [vendor/magento/framework/View/Layout/Builder.php:86]
#9 Magento\Framework\View\Layout\Builder->loadLayoutUpdates() called at [vendor/magento/framework/View/Layout/Builder.php:63]
#10 Magento\Framework\View\Layout\Builder->build() called at [vendor/magento/framework/View/Layout.php:253]
#11 Magento\Framework\View\Layout->build() called at [vendor/magento/framework/View/Layout.php:875]
#12 Magento\Framework\View\Layout->getBlock('page_content_hea...') called at [vendor/magento/module-cms/Helper/Page.php:171]
#13 Magento\Cms\Helper\Page->prepareResultPage(&Magento\Cms\Controller\Index\Index\Interceptor#000000003e5a65a2000000001b0cec1a#,
'vaanyard-applied...') called at
[vendor/magento/module-cms/Controller/Index/Index.php:74]
#14 Magento\Cms\Controller\Index\Index->execute() called at [vendor/magento/framework/App/Action/Action.php:108]
#15 Magento\Framework\App\Action\Action->dispatch(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:58]
#16 Magento\Cms\Controller\Index\Index\Interceptor->___callParent('dispatch',
array(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#))
called at [vendor/magento/framework/Interception/Interceptor.php:138]
#17 Magento\Cms\Controller\Index\Index\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:153]
#18 Magento\Cms\Controller\Index\Index\Interceptor->___callPlugins('dispatch',
array(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#),
array(array('designLoader', 'customerNotifica...',
'catalog_app_acti...', 'tax-app-action-d...', 'weee-app-action-...',
'storeCheck', 'contextPlugin', 'customer-app-act...'))) called at
[generated/code/Magento/Cms/Controller/Index/Index/Interceptor.php:26]
#19 Magento\Cms\Controller\Index\Index\Interceptor->dispatch(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/App/FrontController.php:159]
#20 Magento\Framework\App\FrontController->processRequest(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#,
&Magento\Cms\Controller\Index\Index\Interceptor#000000003e5a65a2000000001b0cec1a#)
called at [vendor/magento/framework/App/FrontController.php:99]
#21 Magento\Framework\App\FrontController->dispatch(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:58]
#22 Magento\Framework\App\FrontController\Interceptor->___callParent('dispatch',
array(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#))
called at [vendor/magento/framework/Interception/Interceptor.php:138]
#23 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at
[vendor/magento/module-store/App/FrontController/Plugin/RequestPreprocessor.php:94]
#24 Magento\Store\App\FrontController\Plugin\RequestPreprocessor->aroundDispatch(&Magento\Framework\App\FrontController\Interceptor#000000003e5a662e000000001b0cec1a#,
&Closure#000000003e5a67cd000000001b0cec1a#,
&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:135]
#25 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at
[vendor/magento/module-page-cache/Model/App/FrontController/BuiltinPlugin.php:73]
#26 Magento\PageCache\Model\App\FrontController\BuiltinPlugin->aroundDispatch(&Magento\Framework\App\FrontController\Interceptor#000000003e5a662e000000001b0cec1a#,
&Closure#000000003e5a67cd000000001b0cec1a#,
&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:135]
#27 Magento\Framework\App\FrontController\Interceptor->Magento\Framework\Interception\{closure}(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/Interception/Interceptor.php:153]
#28 Magento\Framework\App\FrontController\Interceptor->___callPlugins('dispatch',
array(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#),
NULL) called at
[generated/code/Magento/Framework/App/FrontController/Interceptor.php:26]
#29 Magento\Framework\App\FrontController\Interceptor->dispatch(&Magento\Framework\App\Request\Http#000000003e5a66a0000000001b0cec1a#)
called at [vendor/magento/framework/App/Http.php:137]
#30 Magento\Framework\App\Http->launch() called at [vendor/magento/framework/App/Bootstrap.php:261]
#31 Magento\Framework\App\Bootstrap->run(&Magento\Framework\App\Http\Interceptor#000000003e5a665f000000001b0cec1a#)
called at [1010.php:39]
It seems like in one of your layout xml file header blocks, an illegal 'font' element is there.
Check your layout xml files. Specially header_default_block.xml files and basically all xml files for something like '<font'. If it is there, then remove it and see. May be you have to regenerate static content again.
I have a DB farm created with a database (ex: temp). When I try to connect to that using monetdb_startup, get the following error.
src/gdk/gdk_utils.c:1465: GDKfree: Assertion `(asize & 2) == 0' failed.
Aborted (core dumped)
I'm using the sample application tests/readme/readme.c provided.
monetdb_startup("/dbfarm/temp", 0, 0) is what I'm trying to do.
Monet version being used:
MonetDB 5 server v11.29.3 "Mar2018" (64-bit, 128-bit integers)
Stack trace:
#0 0x0000003f39232495 in raise () from /lib64/libc.so.6
#1 0x0000003f39233c75 in abort () from /lib64/libc.so.6
#2 0x0000003f3922b60e in __assert_fail_base () from /lib64/libc.so.6
#3 0x0000003f3922b6d0 in __assert_fail () from /lib64/libc.so.6
#4 0x00007ffff799bc3c in GDKfree (s=0x19602e0) at src/gdk/gdk_utils.c:1465
#5 0x00007ffff79a8521 in freeException (msg=0x19602e0 '▒' <repeats 88 times>, "▒L\001") at src/mal/mal/mal_exception.c:135
#6 0x00007ffff7b38c09 in SQLupgrades (c=0x7ffff42b2400, m=0x1815460) at src/mal/sqlbackend/sql_upgrades.c:1442
#7 0x00007ffff7b1edb2 in SQLinitClient (c=0x7ffff42b2400) at src/mal/sqlbackend/sql_scenario.c:612
#8 0x00007ffff7404f32 in monetdb_connect () at src/embedded/embedded.c:72
#9 0x00007ffff74055da in monetdb_startup (dbdir=0x7fffffffd7c0 "/dbfarm/temp/", silent=0 '\000', sequential=0 '\000')
at src/embedded/embedded.c:162
Thanks
In general, this use case is not supported. So upgrade MonetDBLite databases between versions should work fine, but moving from MonetDBLite to MonetDB and back is probably going to give errors and/or crash.
I am starting to use a dart API for d3.js (found here: https://pub.dartlang.org/packages/d3) and I came across a problem, when I tried to create a Axis using TimeScale.
Console:
oSuchMethodError: method not found: '_proxy'
Receiver: Instance of 'TimeScale'
Arguments: []
timeline.dart code
x = new time.TimeScale()
..range([0, width])
..domain([new DateTime(1999, 0, 1), new DateTime(2014, 0, 0)]);
x = new svg.Axis()
..scale(x);
Log:
#0 Object._noSuchMethod (dart:core-patch/object_patch.dart:44)
#1 Object.noSuchMethod (dart:core-patch/object_patch.dart:47)
#2 getProxy (package:d3/src/js/scale.dart:679:31)
#3 Axis.scale (package:d3/src/js/svg.dart:867:16)
#4 Timeline.attached (http://localhost:20080/frontend/dart/components/timeline.dart:29:9)
#5 Application.init.<init_async_body>.<anonymous closure> (http://localhost:20080/frontend/dart/application/application.dart:128:25)
#6 _HashVMBase&MapMixin&&_LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:351)
#7 Application.init.<init_async_body> (http://localhost:20080/frontend/dart/application/application.dart:105:37)
#8 Future.Future.microtask.<anonymous closure> (dart:async/future.dart:144)
#9 _microtaskLoop (dart:async/schedule_microtask.dart:41)
#10 _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#11 _ScheduleImmediateHelper._handleMutation (dart:html:49308)
[[class]]: _StackTrace(anonymous function) # VM2334:1
VM2334:1 Uncaught Unhandled exception:
Closure call with mismatched arguments: function '_proxy'
NoSuchMethodError: method not found: '_proxy'
Receiver: Instance of 'TimeScale'
Arguments: []
#0 Application.init.<init_async_body>.<anonymous closure> (http://localhost:20080/frontend/dart/application/application.dart:131:21)
#1 _HashVMBase&MapMixin&&_LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:351)
#2 Application.init.<init_async_body> (http://localhost:20080/frontend/dart/application/application.dart:105:37)
#3 Future.Future.microtask.<anonymous closure> (dart:async/future.dart:144)
#4 _microtaskLoop (dart:async/schedule_microtask.dart:41)
#5 _startMicrotaskLoop (dart:async/schedule_microtask.dart:50)
#6 _ScheduleImmediateHelper._handleMutation (dart:html:49308)(anonymous function) # VM2334:1
d3/src/js/scale.dart - line 679
JsObject getProxy(arg) => arg._proxy;
d3/src/js/svg.dart
scale([scale = undefined]) {
var args = [];
if (scale != undefined) {
//line 867
args.add(sc.getProxy(scale));
}
var retval = _proxy.callMethod('scale', args);
if (scale == undefined) {
return retval; // TODO: wrap in Scale
} else {
return new Axis._(retval);
}
}
Did anyone know what's wrong ?
Thanks
Looking at the package code, you will only be able to give a scale parameter that belong to d3/src/js/scale.dart library.
Using a private member like in arg._proxy will retrieve the _proxy attribute only for arg inside the same library (that's what the prepending _ means : private to its library).
Unfortunately I don't see any simple solution to workaround your issue with the current package sources.
The gwan (4.1.18) instance runs for about one day, and then crashed with this tracing information (Not suer how useful it is:( How to get meaningful tracing information?)
----------------
----------------
Sun, 27 Jan 2013 20:07:34 GMT: warning: no loadable sections found in added symbol-file /home/gwan/gwan
0x00007f0018206148 in ?? ()
Id Target Id Frame
* 1 process 2860 "gwan" 0x00007f0018206148 in ?? ()
Thread 1 (process 2860):
#0 0x00007f0018206148 in ?? ()
#1 0x0000000000000004 in ?? ()
#2 0x00007f0018941245 in ?? ()
#3 0x00007f0018206070 in ?? ()
#4 0x00007f000b70ece8 in ?? ()
#5 0x000000000000002e in ?? ()
#6 0x0000000000000000 in ?? ()
Signal : 11:Address not mapped to object
Signal src : 1:.
errno : 0
Thread : 1
Code Pointer: 0000004343c0 (module:gwan, function:??, line:0)
Access Address: 0001004647f0
Registers : EAX=7f000ca04d40 CS=00000033 EIP=0000004343c0 EFLGS=000000010282
EBX=7f000ca08eb0 SS=00000000 ESP=7f000ca04af0 EBP=00000001aeb0
ECX=0000ffffffb0 DS=00000000 ESI=7f000ca04cf0 FS=00000033
EDX=0000000000b0 ES=00000000 EDI=7f000ca04d9c CS=00000033
Module :Function :Line # PgrmCntr(EIP) RetAddress FramePtr(EBP)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
How to get meaningful tracing information?
Leaving the relevant per-thread crash information would surely have helped to give you some insights.
But as you have removed it by hand, I am assuming that you know what you are doing.
Note that running gwan under /home/gwan/gwan -d is not a good idea.
Rather use something like /opt/gwan/gwan -d because the contents of /home are not reachable from other accounts.
And if you are running during days without the parent angel process (-d mode) then it's even less a good idea.
That's not G-WAN-specific:
"you should NEVER run Nginx in production with 'master_process off'"
I get this error when I include
$installer->createEntityTables( $this->getTable('red/red') );
I am using enterprise 1.11
I have also seen alternative to that is type every thing which is really time consuming. Could someone please tell me who to make this function work.
[previous:Exception:private] =>
[xdebug_message] => ( ! ) Mage_Eav_Exception: Can't create table: red_faqs_eavexample in C:\wamp\www\ubt.onlocal.com.au\app\Mage.php on line 549
Call Stack
#TimeMemoryFunctionLocation
10.0003690528{main}( )..\index.php:0
20.00271167384Mage::run( )..\index.php:81
30.01012776112Mage_Core_Model_App->run( )..\Mage.php:640
40.02304545784Mage_Core_Model_App->_initModules( )..\App.php:338
50.46364871080Mage_Core_Model_Resource_Setup::applyAllUpdates( )..\App.php:412
60.528411772936Mage_Core_Model_Resource_Setup->applyUpdates( )..\Setup.php:235
70.528611769664Mage_Core_Model_Resource_Setup->_installResourceDb( )..\Setup.php:327
80.528611769824Mage_Core_Model_Resource_Setup->_modifyResourceDb( )..\Setup.php:421
90.529511778144include( 'C:\wamp\www\ubt.onlocal.com.au\app\code\local\Magelocal\Red\sql\red_setup\install-0.1.0.php' )..\Setup.php:624
100.529711778712Mage_Eav_Model_Entity_Setup->createEntityTables( )..\install-0.1.0.php:6
)
Error in file: "C:\wamp\www\ubt.onlocal.com.au\app\code\local\Magelocal\Red\sql\red_setup\install-0.1.0.php" - Can't create table: red_faqs_eavexample
#0 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\Resource\Setup.php(645): Mage::exception('Mage_Core', 'Error in file: ...')
#1 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\Resource\Setup.php(421): Mage_Core_Model_Resource_Setup->_modifyResourceDb('install', '', '0.1.0')
#2 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\Resource\Setup.php(327): Mage_Core_Model_Resource_Setup->_installResourceDb('0.1.0')
#3 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\Resource\Setup.php(235): Mage_Core_Model_Resource_Setup->applyUpdates()
#4 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\App.php(412): Mage_Core_Model_Resource_Setup::applyAllUpdates()
#5 C:\wamp\www\ubt.onlocal.com.au\app\code\core\Mage\Core\Model\App.php(338): Mage_Core_Model_App->_initModules()
#6 C:\wamp\www\ubt.onlocal.com.au\app\Mage.php(640): Mage_Core_Model_App->run(Array)
#7 C:\wamp\www\ubt.onlocal.com.au\index.php(81): Mage::run('', 'store')
#8 {main}
This is a problem with an error being triggered when it shouldn't be. Long story short, MySQL doesn't support DDL transactions, and in the course of the method DDL routines are being found in the SQL and an error is thrown.
The easy answer is to comment out this line:
lib/Varien/Db/Adapter/PDO/Mysql.php
protected function _checkDdlTransaction($sql)
{
if (is_string($sql) && $this->getTransactionLevel() > 0) {
$startSql = strtolower(substr(ltrim($sql), 0, 3));
if (in_array($startSql, $this->_ddlRoutines)) {
// comment this out: trigger_error(Varien_Db_Adapter_Interface::ERROR_DDL_MESSAGE, E_USER_ERROR);
}
}
}
Doing so allows your module to install. Obviously hacking a core file is a terrible idea. You should extend the method or allow the SQL to run, and then translate the generated SQL into the Magento MySQL API, as seen in core sql setup scripts. The latter is a major pain.. the better idea would be to extend the method.
More here on background information and troubleshooting.