Browse Source
This has been there for ages, but the assertion makes no sense in the context of the test immediately preceding it. This caused an abort() when in -I dts -O dts mode with the right sort of internal labels in a string property value. Add a testcase for this and another candidate edge case (though this one we already get right). Signed-off-by: David Gibson <david@gibson.dropbear.id.au>main
David Gibson
11 years ago
3 changed files with 19 additions and 1 deletions
@ -0,0 +1,14 @@
@@ -0,0 +1,14 @@
|
||||
/dts-v1/; |
||||
|
||||
/ { |
||||
/* Some versions had an off-by-2 bug which caused an abort |
||||
* when outputing labels within strings like this in source |
||||
* format */ |
||||
prop1: prop1 = start1: "foo", mid1: "bar" end1: ; |
||||
|
||||
/* Make sure that we correctly handle source output of things |
||||
* which could almost be expressed as strings, except for the |
||||
* embedded labels */ |
||||
prop2 = start2: [66 6f 6f], mid2: "bar" end2: ; |
||||
}; |
||||
|
Loading…
Reference in new issue